Method and system for computer based testing using customizable templates

ABSTRACT

A system for computer-based testing includes a test driver that delivers the test to an examinee using a display device and controls progression of the test, a template module that stores presentation format information comprising the presentation format of the test, the presentation format information being accessible to the test driver, and a data module that stores data content information comprising the data content of the test, the data content information being accessible to the test driver, the presentation format information combining with the data content information to create the presentation format and the data content of the test. A method of computer-based testing includes retrieving presentation format information from a template module, the presentation format information dividing the display device into a predetermined number of areas in a predetermined arrangement, retrieving data content information from a data module, and combining the presentation format information and the data content information to create the presentation format and data content of the test.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to and claims the priority of U.S.Provisional Application Ser. No. 60/331,228, filed Nov. 13, 2001 andincorporated herein by reference, and is further related to: U.S. patentapplication entitled “EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FORCOMPUTER BASED TESTING” and having inventors Clarke Daniel Bowers,Tronster Maxwell Hartley, Kyle Michael Kvech, and William HowardGarrison U.S. patent application Ser. No. 10/292,911, filed Nov. 13,2002; U.S. patent application entitled “METHOD AND SYSTEM FOR COMPUTERBASED TESTING USING PLUGINS TO EXPAND FUNCTIONALITY OF A TEST DRIVER”and having inventor Clarke Daniel Bowers U.S. patent application Ser.No. 10/292,913, filed Nov. 13, 2002; U.S. Pat. No. 6,966,048, filed Nov.13, 2002, entitled “METHOD AND SYSTEM FOR COMPUTER BASED TESTING USING ANON-DETERMINISTIC EXAM EXTENSIBLE LANGUAGE (XXL) PROTOCOL” and havinginventor Clarke Daniel Bowers; and U.S. Pat. No. 6,948,153, filed Nov.13. 2002, entitled “METHOD AND SYSTEM FOR COMPUTER BASED TESTING USINGAN AMALGAMATED RESOURCE FILE” and having inventor Clarke Daniel Bowersall of which are being filed concurrently herewith and all of which areincorporated by reference in their entirety herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to the field of computer-basedtesting, and in particular, the present invention relates to customizinga visual presentation of a computer-based test using templates thatdefine a presentation format of the computer-based test and plugins thatcontain data content of the computer-based test.

2. Background of the Related Art

For many years, standardized testing has been a common method ofassessing examinees as regards educational placement, skill evaluation,etc. Due to the prevalence and mass distribution of standardized tests,computer-based testing has emerged as a superior method for providingstandardized tests, guaranteeing accurate scoring, and ensuring promptreturn of test results to examinees.

Tests are developed based on the requirements and particulars of testdevelopers. Typically, test developers employ psychometricians orstatisticians and psychologists to determine the specific requirementsspecific to human assessment. These experts often have their own, uniqueideas regarding how a test should be presented and regarding thenecessary contents of that test, including the visual format of the testas well as the data content of the test. Therefore, a particularcomputer-based test has to be customized to fulfill the client'srequirements.

FIG. 1 illustrates a prior art process for computerized testcustomization, denoted generally by reference numeral 10. First, aclient details the desired test requirements and specifications, step12. The computerized test publisher then creates the tools that allowthe test publisher to author the items, presentations, etc., required tofulfill the requirements, step 14. The test publisher then writes anitem viewer, which allows the test publisher to preview what is beingauthored, step 16.

An item presenter is then written to present the new item, for example,to the test driver, step 18. Presenting the new item to the test driverrequires a modification of the test driver's executable code. The testdriver must be modified so that it is aware of the new item and cancommunicate with the new item presenter, step 20. The test packager mustthen also be modified, step 22. The test packager, which may also be acompiler, takes what the test publisher has created and writes theresult as new object codes for the new syntax. Subsequently, the scoringengine must also be modified to be able to score the new item type, step24. Finally, the results processor must be modified to be able to acceptthe new results from the new item, step 26. This process requires noless than seven software creations or modifications to existingsoftware.

Previous test drivers had a fixed look and feel to the visualpresentation of tests. For example, if a particular test driver wasprogrammed to present navigation buttons on the bottom of the testscreen or to place the title bar at the top of the screen, every testdelivered by that test driver would have the identical visualpresentation. However, as stated previously, a client might wish tomodify or customize the visual presentation of a test. A client mightdesire customization for psychometric reasons; for example, the clientknows that examinees function better with exams presented in aparticular way. Or, a client might want a particular visual presentationfor a test for marketing reasons. In previous computer-based testedsystems, the test driver would have to undergo massive reprogramming, asdescribed above, in order to accommodate a particular client's wishes.

U.S. Pat. No. 5,827,070 (Kershaw et al.) and U.S. Pat. No. 5,565,316(Kershaw et al.) are incorporated herein by reference. The '070 and '316patents, which have similar specifications, disclose a computer-basedtesting system comprising a test development system and a test deliverysystem. The test development system comprises a test document creationsystem for specifying the test contents, an item preparation system forcomputerizing each of the items in the test, a test preparation systemfor preparing a computerized test, and a test packaging system forcombining all of the items and test components into a computerized testpackage. The computerized test package is then delivered to authorizedexaminees on a workstation by the test delivery system.

FIGS. 2A and 2B illustrate the screen format during a delivery unit andthe testing tools utilized in the control area, respectively, asdisclosed in the '070 and '316 patents. The screen format during adelivery unit is preferably divided into three main sections; a titleline 30, an item presentation area 32, and a primary control area 34 asillustrated in FIG. 2A. The title line 30 is preferably presented as onesolid gray bar at the top of the screen. It should be understood thatnumerous other color combinations are possible. The title line 30 iscapable of displaying various information comprising the test or takingthe test. For instance, the title line 30 may include the time remainingin the test or test section. Preferably, time is displayed automaticallyalthough an examinee may optionally turn it off. In a preferredembodiment, remaining time is displayed left justified on the title line30 in HH:MM format until the last few minutes of the test. At thatpoint, the display format changes to MM:SS and flashes for three secondsso that the examinee is alerted that the time remaining for taking thetest is nearly over. Other information in the title line 30 may includethe name of the computerized test and program-specified text pertinentto what is being presented (e.g., section name). Information to helporient the examinee is also preferably displayed in title line 30. Forinstance, when an item or tutorial screen is displayed in thepresentation area 32, the notation “xx of yy” or “xx” appears in titleline 30. The “xx” refers to the item number within the test or section,or the screen within the tutorial. The “yy” indicates the total numberof items in the test or section, or screens within the tutorial.Additional orientation information to be provided to the examinee in thetitle line 30 may include the descriptive word such as “HELP” “REVIEW”and “DIRECTION” to indicate a currently displayed screen.

The presentation area 32 of the screen is used to display items screensuch as the text and graphics and non-item screens such as directionscreens, message screens, HELP screens and REVIEW screens. Directionscreens are used to display directions for the test, section, andothers. Message screens display information and examinee options attransition points during the test session to control the flow of thetest. Transition points indicate where a new section or new item is tobe displayed or when the test delivery application moves from an itemscreen to a non-item screen. HELP screens and REVIEW screensrespectively enable an examinee to interact with the HELP and REVIEWfacilities.

The primary control area 34 preferably provides testing tools for givingthe examinee a degree of control over the testing session. In apreferred embodiment, there are ten testing tools (also referred to as“primary controls”). Each tool has its own icon. Icons are pictorialrepresentation of a function available to a user, which can be activatedby selecting that icon. Referring to FIG. 2B, the NEXT icon 54, the PREVicon 52, the REVIEW icon 42 and HELP icon 50 can be used by the examineeto move from one screen to another screen. When the NEXT icon 54 isselected, the examinee can move on to the next screen. Selecting thePREV icon 52 enables the examinee to move back to the previous screen.The HELP icon 50 can be selected by the examinee to invoke the HELPfacility. When HELP is invoked, the examinee moves to a HELP screen toretrieve previously presented direction and information about topicscovered in the tutorials. The examinee is returned to the screen fromwhich HELP was invoked when the Help screen is exited. The MARK icon 44enables the examinee to mark an item for review. In a preferredembodiment, both answered and unanswered items can be marked. A markeditem is indicated on an item screen by displaying a checkmark in theMARK icon 44. The checkmark may also appear next to the marked item inthe Review screen when the REVIEW facility is invoked after an item hasbeen marked. The examinee can unmark an item by clicking on the MARKicon 44 a second time. However, preferably the examinee need not unmarkitems in order to leave a section. The REVIEW icon 42, when selected,presents the review screen to the examinee listing the items in thesection in the order they were presented to the examinee, along with anygroup or set paraphrase associated with item and an indication ofwhether the item has been marked by the examinee from the item screen.The examinee then has the ability to go directly to any item in a testsection by clicking, as described above. Preferably, the examinee caninvoke the REVIEW facility from any item screen, and the REVIEW screenwill display the status of all the items in the section regardless ofwhether all of the items had been presented. In a further preferredembodiment, the examinee may skip some items by advancing to asubsequent item. The ERASE icon 46 enables the examinee to reset allselected choices for the current item to their original state. The TIMEicon 40 allows the examinee to turn on and off the remaining timedisplay in the title line 30. The EXIT icon 38 allows the examinee toleave the current section of the test. The QUIT icon 36 allows theexaminee to quit the test. The CALC icon 48 allows the examinee to useon-screen calculator.

A testing tool is said to exist if it appears on every screen. Theexistence of each of the depicted icons; PREV, CALC, QUIT, EXIT, TIME,REVIEW, MARK and ERASE is specified by each test script or the sectionconfiguration file. The NEXT and HELP tools preferably exist in alltests. Testing tools that do not exist should not appear on the screen,and in a preferred embodiment, the location of the remaining tools isadjusted to close any gaps left by non-existent tools. Test scripts candefine the existence of tools to limit the ways in which examinees cannavigate through the test. For example, a program can define aforward-progression-only test by eliminating the PREV and REVIEW tools.A testing tool is said to be available if it exists and can be used.Preferably, a testing tool is displayed in black if available and ingray when it is not. For instance, in preferred embodiments, the NEXTicon 54, the PREV icon 52, ERASE icon 46, MARK icon 44, and the CALCicon 48 are available only from item screens. However, the HELP icon 50is available from all screens. The REVIEW icon 42 is available from itemscreens and group or set directions screens while the TIME icon 40 mayor may not be available from directions screens depending upon whetherthe section configuration file indicates timing is to start before orafter the presentation of directions.

U.S. Pat. No. 5,513,994 (Kershaw et al.), which is incorporated hereinby reference, discloses a centralized administrative system and methodof administering standardized test to a plurality of examinees. Theadministrative system is implemented on a central administrationworkstation and at least one test workstation located in different roomsat a test center. The administrative system software, which providessubstantially administrative functions, is executed from the centraladministration workstation. The administrative system software, whichprovides function carried out in connection with a test session, isexecuted from the testing workstations.

None of the Kershaw et al. patents appear to make any mention of howmodifications may be made to the computer-based testing system toincorporate a particular client's test specification regarding thevisual presentation of the test. The '070 and '316 patents only disclosea screen format that is preferably divided into three main sections: atitle line, an item presentation area, and a primary control area, wherethe control area contains a specific set of non-customizable tools. Thepatents make no mention of being able to customize, for example, thetitle line or the primary control area, to allow different versions ofthese sections to be presented to an examinee during a single test.

What is required is a system that allows the test publisher or publisherto have full control over the visual presentation of the content,navigation controls, titles, and other ancillary display informationthat are delivered to an examinee during a test.

SUMMARY OF THE INVENTION

It is one feature and advantage of the present invention to enableexpansion of a test driver in a computer-based test delivery systemwithout necessitating changes to an executable code of the test driverand without recompiling or re-linking the test driver.

It is another optional feature and advantage of the present invention tofacilitate expansion of the test driver using an expansion module.

It is another optional feature and advantage of the present invention toprovide test presentation information in an eXam eXtensible testdefinition language.

It is another optional feature and advantage of the present invention topresent a visual format of the test to an examinee using templates thatdetermine the layout of the display device.

It is another optional feature and advantage of the present invention tocombine the templates with visible plugins to create presentations todeliver to the examinee during the test.

It is another optional feature and advantage of the present invention touse HTML rendering capabilities and scripts to create the visual formatof the test.

It is another optional feature and advantage of the present invention tohost Microsoft web browser control to further enable the visual formatof the test.

It is another optional feature and advantage of the present invention touse monikers to persist data from an exam resource file to furtherenable the visual format of the test.

It is another optional feature and advantage of the present invention toexpose test driver object models to a scripting environment to furtherenable the visual format of the test.

These and other features and advantages of the present invention areachieved in a system for computer-based testing for delivering a test toan examinee. The test has a presentation format and data content. Thesystem includes a test driver that delivers the test to an examineeusing a display device and controls progression of the test. The systemalso includes a template module that stores presentation formatinformation comprising the presentation format of the test, thepresentation format information being accessible to the test driver. Thesystem further includes a data module that stores data contentinformation comprising the data content of the at least one test, thedata content information being accessible to the test driver, thepresentation format information combining with the data contentinformation to create the presentation format and the data content ofthe at least one test.

In another embodiment of the present invention, a system forcomputer-based testing includes a test driver that delivers the test toan examinee using a display device and controls progression of the test.The system also includes a template module that stores presentationformat information comprising the presentation format of the test, thepresentation format information being accessible to the test driver. Thesystem further includes a data module that stores data contentinformation comprising the data content of the test, the data contentinformation being accessible to the test driver. The data contentinformation combines with the presentation format information to createthe presentation format and data content of the at least one test. Thesystem also includes a resource file that stores the progression of thetest, the resource file providing the presentation format information tothe template module and providing the data content information to thedata module. The system further includes an instance file that storesexamination state information comprising responses provided by theexaminee to items presented to the examinee during the at least onetest.

In another alternative embodiment of the present invention, a systemincludes a test driver that delivers the at least one test to anexaminee using a display device and controls progression of the at leastone test. The system also includes a template module that storespresentation format information comprising the presentation format ofthe at least one test. The presentation format information divides thedisplay device into a predetermined number of areas in a predeterminedarrangement and is accessible to the test driver. The system furtherincludes a first data module that stores first information comprisingnon-interactive display material of the at least one test, the firstinformation being accessible to the test driver and a second data modulethat stores second information comprising test navigation controls ofthe at least one test, the second information being accessible to thetest driver. The system also includes a third data module that storesthird information comprising items of the at least one test, the thirdinformation being accessible to the test driver. The first information,the second information, and the third information combine with thepresentation format information to create the presentation format anddata content of the at least one test such that the non-interactivedisplay material, the test navigation controls, and/or the itemscomprise separate ones of the predetermined number of areas.

In another alternative embodiment of the present invention, a systemincludes a test driver that delivers the at least one test to anexaminee using a display device and controls progression of the test.The system also includes a template module that stores presentationformat information comprising the presentation format of the test, thepresentation format information accessible to the test driver. Thesystem further includes a data module that stores data contentinformation comprising the data content of the test, the data contentinformation accessible to the test driver. The system also includes apresentation module that stores presentation information determiningwhat is seen by the examinee on the display device during delivery ofthe at least one test. The presentation information is defined bycombining the presentation format information and the data contentinformation is provided to the test driver such that the test driverprovides the presentation information to the examinee using the displaydevice.

In another embodiment of the present invention, a method ofcomputer-based testing is provided for delivering a test to an examinee.The test has a presentation format and data content and is controlled bya test driver, which delivers the test to the examinee using a displaydevice and controls progression of the test. The method includesretrieving presentation format information comprising the presentationformat of the at least one test from a template module, the presentationformat information dividing the display device into a predeterminednumber of areas in a predetermined arrangement. The method also includesretrieving data content information comprising the data content of theat least one test from a data module and combining the presentationformat information and the data content information to create thepresentation format and data content of the at least one test.

There has thus been outlined, rather broadly, the more importantfeatures of the invention and several, but not all, embodiments in orderthat the detailed description thereof that follows may be betterunderstood, and in order that the present contribution to the art may bebetter appreciated. There are, of course, additional features of theinvention that will be described hereinafter and which will form thesubject matter of the claims appended hereto.

In this respect, before explaining at least one embodiment of theinvention in detail, it is to be understood that the invention is notlimited in its application to the details of construction and to thearrangements of the components set forth in the following description orillustrated in the drawings. The invention is capable of otherembodiments and of being practiced and carried out in various ways.Also, it is to be understood that the phraseology and terminologyemployed herein are for the purpose of description and should not beregarded as limiting.

As such, those skilled in the art will appreciate that the conception,upon which this disclosure is based, may readily be utilized as a basisfor the designing of other structures, methods and systems for carryingout the several purposes of the present invention. It is important,therefore, that the claims be regarded as including such equivalentconstructions insofar as they do not depart from the spirit and scope ofthe present invention.

Further, the purpose of the foregoing abstract is to enable the U.S.Patent and Trademark Office and the public generally, and especially thescientists, engineers and practitioners in the art who are not familiarwith patent or legal terms or phraseology, to determine quickly from acursory inspection the nature and essence of the technical disclosure ofthe application. The abstract is neither intended to define theinvention of the application, which is measured by the claims, nor is itintended to be limiting as to the scope of the invention in any way.

These, together with other objects of the invention, along with thevarious features of novelty, which characterize the invention, arepointed out with particularity in the claims annexed to and forming apart of this disclosure. For a better understanding of the invention,its operating advantages and the specific objects attained by its uses,reference should be had to the accompanying drawings and descriptivematter in which there is illustrated preferred embodiments of theinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram of a prior art method of computerized testcustomization;

FIG. 2A is an illustration of a prior art display of a computer-basedtest;

FIG. 2B is an illustration of a prior art display of test navigationcontrols;

FIG. 3 is a schematic diagram of a computer-based testing systemaccording to the present invention;

FIG. 4 is a block diagram illustrating different types of plugins thatare used with the computer-based testing system according to the currentinvention;

FIG. 5 is an illustration of Active Documents as utilized in the presentinvention;

FIG. 6 illustrates various components that comprise an exam source file;

FIGS. 7A and 7B are schematics illustrating the components, classes, andinterfaces that comprise a test definition language compiler accordingto the present invention;

FIG. 8 is a schematic illustrating the components that comprise a testdriver and a test administration system according to the presentinvention;

FIGS. 9A and 9B are schematics illustrating the classes and interfacesthat comprise the test driver;

FIG. 10 illustrating the interfaces that comprise a structured storageaccording to the present invention;

FIGS. 11A and 11B are schematics illustrating the classes and interfacesthat comprise the structure storage and associated operations;

FIG. 12 is a block diagram of main storage branches of an exam resourcefile according to the present invention;

FIG. 13 is a block diagram illustrating an exams branch of the examresource file;

FIGS. 14A and 14B is a block diagram illustrating a forms branch of theexam resource file;

FIG. 15 is a block diagram illustrating an items branch of the examresource file;

FIG. 16 is a block diagram illustrating a categories branch of the examresource file;

FIG. 17 is a block diagram illustrating a templates branch of the examresource file;

FIG. 18 is a block diagram illustrating a sections branch of the examresource file;

FIG. 19 is a block diagram illustrating a groups branch of the examresource file;

FIGS. 20A, 20B, 20C, and 20D are block diagrams illustrating an eventssub-branch of the groups branch of the exam resource file;

FIG. 21 is a block diagram illustrating a plugins branch of the examresource file;

FIG. 22 is a block diagram illustrating a data branch of the examresource file;

FIG. 23 is a block diagram illustrating a formGroups branch of the examresource file;

FIG. 24 is a block diagram illustrating an attributes branch of the examresource file;

FIG. 25 is a block diagram illustrating a scripts branch of the examresource file;

FIG. 26 is a block diagram illustrating a message box branch of the examresource file;

FIGS. 27A, 27B, 27C, and 27D are block diagrams of an exam instance fileaccording to the present invention;

FIG. 28 is a flow diagram of a method of computerized test customizationaccording to the present invention;

FIG. 29 is a flow chart of a method of test production and test deliveryaccording to the present invention;

FIG. 30 is a flow chart of a method of validation of test specificationand content according to the present invention;

FIG. 31 is a flow chart of a method of test delivery according to thepresent invention;

FIG. 32 is a flow chart of a method of creating and delivering apresentation according to the present invention;

FIG. 33 is a diagram of a life cycle of a plugin according to thepresent invention;

FIG. 34 is a flow diagram of a process for compiling plugins accordingto the present invention;

FIGS. 35A, 35B, 35C, and 35D are flow diagrams of a process fordelivering plugins to an examinee during a computer-based test;

FIG. 36 is an illustration of various areas as used to create displaysaccording to the present invention;

FIG. 37 is an illustration of containing visible plugins within areas tocreate displays according to the present invention;

FIG. 38 is an illustration of templates used to create displaysaccording to the present invention;

FIG. 39 is an illustration of how plugins are used with templates tocreate displays according to the present invention;

FIG. 40 is an example of a presentation created according to the presentinvention;

FIG. 41 illustrates how a test definition language is rendered to createa display according to the present invention;

FIG. 42 is an example of a presentation of a multiple choice item usinggraphical distractors created according to the present invention;

FIG. 43 is an example of a presentation of a review screen createdaccording to the present invention;

FIG. 44 is an example of a presentation of a multiple choice item usingHTML created according to the present invention;

FIG. 45 is an example of a presentation of a multiple choice item usingHTML with frames and hyperlinks created according to the presentinvention;

FIG. 46 is an example of a presentation of a multiple choice item usingHTML with frames and unlimited distractors created according to thepresent invention; and

FIG. 47 is an example of a presentation of an item using an embeddedExcel spreadsheet created according to the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference now will be made in detail to the presently preferredembodiments of the invention. Such embodiments are provided by way ofexplanation of the invention, which is not intended to be limitedthereto. In fact, those of ordinary skill in the art may appreciate uponreading the present specification and viewing the present drawings thatvarious modifications and variations can be made.

For example, features illustrated or described as part of one embodimentcan be used on other embodiments to yield a still further embodiment.Additionally, certain features may be interchanged with similar devicesor features not mentioned yet which perform the same or similarfunctions. It is therefore intended that such modifications andvariations are included within the totality of the present invention.

The present invention discloses a system and method of computer-basedtesting using a test driver that is, for example, object-oriented and isarchitected to dynamically add functionality through, for example, theuse of an expansion module, and preferably through the use of plugins.The test driver preferably references component object model serversusing standard interfaces, and uses, for example, class names (that canbe an Active Document) defined in a custom test definition languageentitled eXtensible eXam Language (“XXL”) based on eXtensible MarkupLanguage (“XML”) format to interact with existing applications whileoffering the flexibility of allowing development of new plugins. Thesenew plugins can be customized to a client's needs without changing thecore test driver. The specific format and protocol of XXL is alsodescribed in the co-pending application filed on the same date, entitled“EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FOR COMPUTER BASED TESTING,”incorporated herein by reference.

The plugins advantageously enable the test driver to support, forexample, new item types, navigation algorithms, information displays,scoring algorithms, timing algorithms, test unit selection algorithms,results persistence reporting, printed score reporting, and/or helmtypes without change to the test driver's executable. Plugins also allowexpansion of the test driver's functionality without requiring the testdriver to be recompiled or re-linked, and without requiring the testpublisher to learn to program. Since plugins are written independentlyof the test driver, plugins can be written long after the test driver isbuilt.

The client and the software developer can design and test the pluginsand distribute the plugins to each test site. By using this method,large-scale regression testing of other examinations will not usually benecessary unless changes are made to the plugins that may be used bymany examinations.

I. Overview of Computer-Based Test Delivery System

FIG. 3 shows an overview of the software architecture for thecomputer-based test delivery system of the present invention, denotedgenerally by reference numeral 100. Test driver 110 is responsible forcontrolling all aspects of the computer-based test. Test driver 110identifies examinees scheduled to take the computer-based test andidentifies and creates the appropriate test. Test driver 110 thenpresents all of the test components to examinees using a display device(not shown), such as a computer monitor, and enables examinees to enterresponses to test questions through the use of an input device (notshown), such as a keyboard, a mouse, etc. Test driver 110 also monitorsthe security of the test. For example, test driver 110 can preventaccess to the Internet and can validate examinees, although, thesefunctions are preferably performed by the test center administrationsystem. Test driver 110 also monitors the timing of the test, providingrelevant warnings to examinee regarding the elapsed time of the test andthe time remaining for a particular section of the test or for theentire test. Test driver 110 is also responsible for scoring the test,once the test is completed or while the test is in progress, and forreporting the results of the test by physical printout using printer 182or in a file format using candidate exam results file 180. If the testis interrupted while in progress, for example, due to a power failure,test driver 110 restarts the test, preferably at the point at which thetest was interrupted, as will be described subsequently in more detail.Finally, if the test is left incomplete, test driver 110 cleans up theincomplete test. An incomplete test will have an exam instance file inthe examinee's directory but will not have created a results file. Aresults file is created even though generally the candidate will fail.The number of items delivered to the examinee is recorded in the resultsfile. Test driver 110 picks up where the event was interrupted andinvisibly deliveries the rest of the units of the test.

A test specification is authored by a test publisher according to thespecifications of the client and stored in exam source files 130. Examsource files 130 include data files 132, XXL files 134, multimedia files136, and hypertext markup language (“HTML”) files 138. XXL files 134include the test specification, which contains the client's requirementsfor the test, a bank of test items or questions, templates thatdetermine the physical appearance of the test, plugins, and anyadditional data necessary to implement the test. Additional data is alsostored in data files 132. For example an adaptive selection plugin mayneed a, b & c theta values. These values are stored in a binary filecreated by a statistical package.

HTML files 130 include, for example, any visual components of the test,such as the appearance of test items or questions, the appearance ofpresentations on the display device, the appearance of any clientspecified customizations, and/or the appearance of score reports. HTMLfiles 130 preferably also include script, for example, VBscript andJscript, or Java script. HTML files 130 are preferably authored usingMicrosoft's FrontPage 2000. FrontPage 2000 is preferably also used tomanage the source files in a hierarchy that is chosen by the testpublisher. Multimedia files 136 include, for example, any images (.jpg,.gif, etc.) and/or sound files (.mp3, .wav, .au, etc.) that are usedduring the test.

XXL compiler 140 retrieves XXL files 134 from exam source files 130using interface 190 and compiles the XXL test content stored in XXLfiles 134. XXL compiler 140 stores the compiled test files in examresource file 120. In another embodiment, exam source files 130 do notcontain XXL files 134 and contains, for example, only multi-media files.In this embodiment, XXL compiler 140 is merely a test packager thatwrites the data directly to exam resource file 120 without modificationor validation. The data appears in a stream under the “data” branch ofexam resource file 120. The name of the stream is specified by the testauthor.

In a preferred embodiment, XXL files 134 also include XXL language thatdefines plugins 150, in which case, plugins 150 assist XXL compiler 140in compiling XXL files 134. Test driver 110 preferably supports, forexample, nine different types of plugins 150, including, for example:display plugin 152; helm plugin 154; item plugin 156; timer plugin 158;selection plugin 160; navigation plugin 162; scoring plugin 164; resultsplugin 166; and report plugin 168. Plugins 150, which are also includedin XXL files 134, are the first XML files compiled into exam resourcefile 120.

Plugins 150 allow a test designer to customize the behavior of testdriver 110 and are divided into two types, for example: visible pluginsand invisible plugins, as shown in FIG. 4. The visible plugins, whichinclude display plugin 152, helm plugin 154, and item plugin 156, enablethe test driver to control what is presented visually to an examinee onthe display device. The invisible plugins, which include timer plugin158, selection plugin 160, navigation plugin 162, scoring plugin 164,results plugin 166, and report plugin 168, enable the test driver tocontrol more functional aspects of the test. Plugins 150 are used tovalidate data stored in exam source files 130 that is to be used by oneof plugins 150 during delivery of the test to the examinee, as isdescribed below in greater detail. Plugins 150 are, preferably,component object model (“COM”) objects, as described below. Plugins 150,may also utilize Java implementation. Plugins 150 are preferably writtenusing Microsoft Visual C++ or Visual Basic 6.0 or any fully COM enabledlanguage. Plugins 150 may be in or out-of-process, and, therefore, canexist as executable (“.EXE”) files or as dynamic link library (“.DLL”)files.

An application or component that uses objects provided by anothercomponent is called a client. Components are characterized by theirlocation relative to clients. An out-of process component is an .exefile that runs in its own process, with its own thread of execution.Communication between a client and an out-of-process component istherefore called cross-process or out-of-process communication.

An in-process component, such as a .dll or .ocx file, runs in the sameprocess as the client. It provides the fastest way of accessing objects,because property and method calls don't have to be marshaled acrossprocess boundaries. However, an in-process component must use theclient's thread of execution.

Exam resource file 120 receives the compiled test content from XXLcompiler 140 and plugins 150, if applicable, and stores the compiledtest content in an object-linking and embedding (“OLE”) structuredstorage format, called POLESS, which is described in greater detailbelow. Other storage formats may optionally be used. OLE allowsdifferent objects to write information into the same file, for example,embedding an Excel spreadsheet inside a Word document. OLE supports twotypes of structures, embedding and linking. In OLE embedding, the Worddocument of the example is a container application and the Excelspreadsheet is an embedded object. The container application contains acopy of the embedded object and changes made to the embedded objectaffect only the container application. In OLE linking, the Word documentof the example is the container application and the Excel spreadsheet isa linked object. The container application contains a pointer to thelinked object and any changes made to the linked object change theoriginal linked object. Any other applications that link to the linkedobject are also updated. POLESS supports structured storage such thatonly one change made to an object stored in exam resource file 120 isglobally effective. Test driver 110 comprises Active Document containerapplication 112 for the visible plugins, display plugin 152, helm plugin154, and item plugin 156, which function as embedded objects, preferablyCOM objects.

FIG. 5 shows an example of Active Document container application 112being used with several item plugins 156. Each item plugin 156, in thiscase representing a multiple choice (“multi-choice”) item, a hot areaitem, and a fill in the blank item, are linked to Active Documentcontainer application 112 through the IItem and IPlugin COM interfaces169.

Both XXL compiler 140 and plugins 150 are involved in storing thecompiled test content into exam resource file 120, if any of plugins 150are being used. Exam resource file 120 comprises, for example, ahierarchical storage structure, as will be described in further detailbelow. Other storage structures may optionally be used. XXL compiler 140determines to which storage location a specific segment of the compiledtest content is to be stored. However, if any of plugins 150 are used tovalidate the portion of any of the data from exam source files 130, thenthe plugins 150 store the data directly to the exam resource file, basedupon directions from XXL compiler 140. XXL compiler usesIPersistResource interface 192, co-located with I-Plugin interface 167in FIG. 3, to control the persistence of the data to exam resource file120. XXL compiler 140 and plugins 150 write the data to exam resourcefile 120 using POLESS interfaces 191.

FIG. 6 illustrates the contents of exam source file 130, which arecompiled into exam resource file 120 by XXL compiler 140 and plugins150. FrontPage 2000 Web 200 is used, for example, to author the test.Exam source files 130 contain media files 210, visual files 220, andlogic files 230. Media files 210 are multimedia files used to enhancethe presentation of the test, including, for example, XML data files212, sound files 214, image files 216, and binary files 218. XML datafiles 212 include the XXL extensions from the plugins 150 that use XML.The test specification, presentation, scoring and other information isspecified in the XML files. Sound files 214 include any sounds that areto be used during the test, such as .mp3 files, .au files, etc. Imagefiles 216 include any images to be used during the test, such as .jpgfiles, .gif files, etc. Binary files 218 include any data needed by aplugin 150 that is not in XXL format. Visual files 220 are HTML filesthat specify the visual presentation of the test as presented to theexamine on the display device, including items files 222, presentationfiles 224, score report files 226, and custom look files 228. Itemsfiles 222 include HTML files that are used to specify the visualcomponent of test questions, e.g., stems and distractors. Items files222 are capable also of referencing external exhibits. An exhibit couldbe a chart, diagram or photograph. Formats of exhibits include, forexample: .jpg, .png, etc. Presentation files 224 define what is seen bythe examinee on the display device at a particular instant during thetest. Score report files 226 is typically an HTML file with embeddedscript that includes, for example candidate demographics, appointmentinformation, and candidate performance. The performance might includepass/fail, achievement in different content areas, etc. Custom lookfiles 228 are typically HTML files with embedded script to layout, forexample, the title bar and information contained therein. Logic files230 are XML files that specify the functional aspects of the test,including test specification files 232, plugin files 234, item bankfiles 236, and template files 238. Test specification files 232 specifythe content and progression of the test as provided by the client.Plugin files 234 define plugins 150 and contain any data necessary toimplement plugins 150. Item bank files 236 include the data content andproperties of the items, or test questions, that are to be presented tothe examinee during the test. Properties of an item include the correctanswer for the item, the weight given to the item, etc. Template files238 define visual layouts that are used with the display screen duringthe test.

Referring again to FIG. 3, once a test has begun, test driver 110accesses exam resource file 120 for the instructions and files needed toimplement the test, using POLESS interfaces 193. Test driver 110 alsoaccesses plugins 150 for additional data that expands the functionalityof test driver 110 in the areas of items, navigation algorithms,information displays, scoring algorithms, timing algorithms, test unitselection algorithms, results persistence reporting, printed scorereporting, and/or helm types. Test driver 110 communicates with plugins150 using various COM interfaces 169. COM interfaces facilitate OLElinking. As stated previously, test driver 110 is an Active Documentcontainer application and plugins 150 are embedded objects. The COMinterfaces function as communications paths between the containerapplication and the linked objects.

There are, for example, ten COM interfaces utilized in computer-basedtest delivery system 100. IPlugin interface 167, which is also a COMinterface, is supported by all of plugins 150. COM interfaces 169,therefore, includes the IPlugin interface. The IPlugin interfacecontains generic operations such as loading and unloading required ofall plugins 150. In addition to the global IPlugin interface, eachplugin 150 also uses, for example, a second, individual COM interface169 to communicate with test driver 110. Alternative structures of theIPlugin interface may also be used. Table 1 shows the relationshipbetween each plugin 150 and the COM interface 169 used with thatparticular plugin 150.

TABLE 1 COM INTERFACE FOR PLUGINS PLUGIN COM INTERFACE DESCRIPTION AllPlugins 150 IPlugin Passes data between the test driver and all pluginsregarding generic operations, e.g., loading and unloading. Display 152IDisplay Passes data between the test driver and the visible pluginsthat handle title bars, displays, non-answered items, and summaries.Helm 154 IHelm Passes data between the test driver and the visibleplugins that display navigation controls or reviews. Communicates with anavigation plugin to perform the actual navigation. Also functions as auser interface connection to the test driver. Item 156 IItem Passes databetween the test driver and the visible plugins that govern test itemsor simulations. Timer 158 IUnitTimer Passes data between the testdrivers and the invisible plugins used to perform timing acrossexamination sections. Selection 160 ISelection Passes data between thetest drivers and the invisible plugins used to select forms, sections,groups, or items for delivery to the examinee. Navigation 160 INavigatePasses data between the test drivers and the invisible plugins used tocontrol section navigation and define rules for traversing through thetest. Scoring 164 IScore Passes data between the test drivers and theinvisible plugins used to control scoring of delivered testing units.Results 166 IResults Passes data between the test drivers and theinvisible plugins that control writing of examinee results, for example,to candidate exam results file 180. Report 168 IReport Passes databetween the test drivers and the invisible plugins that control printingof score reports and other material, for example, printed referencematerial and post exam instructions to printer 182.

Exam instance file 170 is used to restart a test if the test has beeninterrupted, for example, because of a power failure. During delivery ofthe test, exam instance file 170 receives examination state informationfrom test driver 110 and plugins 150 regarding the state of all runningobjects being used to deliver the test. The examination stateinformation includes the presentation that was being delivered on thedisplay device before the interruption, the responses the examinee hadentered in that presentation, etc. When the test is restarted, the examinstance file 170 loads the state information back to test driver 110and plugins 150, allowing the test to return to operation at the pointwhere the test had been interrupted. Preferably, the running state ofall objects is saved to exam instance file 170 rather than of only someof the objects. Saving the state of only some of the objects to examinstance file 170 causes the potential problem of only a portion of thetest information being restored after a test interruption. Exam instancefile 170 may also store additional information relating to the test,including, for example: the timing utilized and time remaining on unitsof the exam, the current unit of delivery, candidate score, etc. Testdriver 110 and plugins 150 communicate with exam instance file 170 usingPOLESS interfaces 195. Test driver 110 controls communications betweentest driver 110 and plugins 150 using IPersistInstance interface 196,which is collocated with COM interfaces 169 in FIG. 3.

Several administrative environments perform the administrative functionsof computer-based test delivery system 100, for example: Test CenterManager (“TCM”) Bridge 172; Educational Testing Service (“ETS”) Bridge174; and Unified Administration System (“UAS”) 174. Administrativefunctions include, for example: checking-in an examinee, starting thetest, aborting the test, pausing the test, resuming the test, andtransmitting results.

There are preferably two ways to run Test driver 110. The first isthrough a series of command line options and the second is using COMinterfaces describing appointment information. The command line optionexists for backwards compatibility in a standard ETS environment and aTCM environment. Table 2 shows a list of command line options testdriver 110 supports. There are, for example, four programs which launchthe test through the COM interface, for example: 1) LaunchTest.exe (fortest production and client review); 2) UAS; 3) UTD2ETS.dll (an internalcompatibility module for use with the ETS administration environment);and 4) UTD2TCM (for the Test Center Manger environment). Other number ofenvironments and/or programs may optionally be used.

Switch(es) Option(s) Purpose /? /help n/a Displays command line switchesin dialog box. /UnregServer n/a Unregisters the test driver core COMserver. /Regserver n/a Registers the test driver core COM server. /Tform name Name of the form or form group to run in the exam. /F resourcefile The exam resource file to use. /S n/a Suppress any printing. /W n/aRun in close-of-day mode. /TI n/a Set tracing level to information.(Very large instance file). /TW n/a Set tracing level to warning. (Largeinstance file.) /TE n/a Set tracing level to error. (Average sizedinstance file.) /K resource dir, Used to point to directories. A spaceSKSID, separates each of the three options. candidate director

The administration environments use several interfaces to communicatewith test driver 110. IAppointment interface 176 is part of UAS 174 andallows access by test driver 110 to examinee information for theexaminee taking the test, such as demographics. The examinee informationis included in candidate exam results file 180, which is created by thetest driver. ILaunch2 interface 177 functions as the primary controlinterface for UAS 174 and allows UAS 174 to control various componentssuch as test driver 110, screen resolution change, accommodations fordisabled candidates, examinee check-in, etc., in a test center, which isthe physical location where the examinee is taking the test. ITransferinterface 199 transfers candidate exam results file 180 and other filesback to UAS 174. IPrint interface 198 sends information regarding anyreports to printer 182.

II. XXL Compiler Interfaces and Classes

FIGS. 7A and 7B illustrate the main diagram for XXL compiler 140. XXLcompiler 140 comprises the following classes, for example: ccompile2000; cData 2004; cArea 2006; cTemplate 2008; cCategory 2010; citem2012; cPresentation 2014; cGroup 2016; cSection 2018; cForm 2020;cFromGroup 2022; cExam 2024; cMsgBox 2026; cChecksum 2028; cEvent 2030;cResutl 2032; cReport 2024; cPlugin 2036; and cXXL 2038.

The main interface to XXL compiler 140 is ICompile interface 2002.ICompile interface 2002 is implemented by CCompiler class 2000. Allcontrol and initiation of compilation of exam source files 130 into examresource file 120 occurs by way of this single public interface. Thecore, non-plugin related elements of the XXL test definition language,as stored in XXL files 134, are compiled by classes in XXL compiler 140.For example, cSection class 2018, compiles the section element, andcGroup class 2016 compiles the group element.

ICompile interface 2002 supports the following operations, for example:createResource( ); addSource( ); addData( ); closeResource( ); about( );linkResource( ); openResource( ) and getCryptoObject( ). CreateResource() creates a resource file, for example, an XXL based resource file suchas exam resource file 120. AddSource( ) compiles an XXL file into theresource file. AddData( ) adds a file directly to a data branch of theresource file. CloseResource( ) closes the resource file. LinkResource() links a resource in the resource file and is performed after allcompiling of the source files are completed. GetCryptoObject( ) returnsan ICrypto object containing the current encryption setting of POLESS,as described below.

The classes of XXL compiler 1040, e.g., cForm 2020 and citem 2012,handle individual XXL core language elements. All of these classescompile the specific XXL source element into exam resource file 120. Allof these class language elements are also symbols used in laterreferences. Therefore, the classes all derive from cSymbol class 2040.cSymbol class 2040 allows the classes of XXL compiler 140 to reside in asymbol table.

For example, the XXL element plugin 150 appears as follows in XXL files134:

<plugin name=“helmNextPrevious” progid=“UTDP.cNextPrevious”  />This XXL call causes an instance of cPlugin class 2036 to be created,compiles the source, and writes the compiled result to exam resourcefile 120. The name and ID of Plugin 150 is also added to the symboltable for later reference.

XXL compiler 140 also contains the following token classes, for example:cToken 2042; cTokenCreatorNoRef 2044; cTokenCreator 2046;CtokenCreatorRef 2048; cTokenCreatorBase 2050; and cTokenFactory 2054.These token classes are involved in the identification of tokens. Tokensturn into symbols after identification. Symbols are any class derivedfrom cSymbol, e.g., cTemplate, cSection, etc.

XXL compiler 140 also contains the following symbol table classes, forexample: cPluginSymbolTable 2058; cTemplateSymbolTable 2060;cSymbolTable 2062; cFFGSymbolTable 2064; cSGPSymbolTable 2066; andcSymbolTableBase 2068. These classes are varities of symbol tables.There are different symbol tables for different groups of symbols. Agroup of symbols define a name space for the symbol. Common symbol tablefunctions are located in the base symbol table classes and templates.

All content and specification destined for a plugin 150 appears in thedata element in XXL. For example, below is an item definition in XXL:

<item name=“wantABreak1” skipAllowed=“false”> <data> <multiChoicecorrectAnswer=“A” maxResponses=“1” minResponses=“1” autoPrompt=“false”URI=“itembank/info_item.htm#wantABreak”/> </data> </item>The item element is handled by a citem class 2012 object. The dataelement in the XXL definition is handled by a cData class 2004 object.Item plugin 156 Plugin 150 will receive the source to compile from thecData class 2004 object, in this example, a multiChoice element.

cWrapXML class 2052, a wrapper class for XML DOM nodes, supports errorhandling. cCustomAttributes class 2056 compiles the custom attributesXXL element. cWrapPropertySet class 2070 is a wrapper class for a POLESSproperty storage.

III. Test Driver Interfaces and Classes

A. Interfaces

FIG. 8 shows test driver 110, UAS 174, and the interfaces used by andbetween the test driver 110 and UAS 174 to deliver the test. UAS 174defines ILaunch2 interface 177, which is used by UAS 174 to initiatetest events. ILaunch2 interface 177 is an extension of ILaunch interface178, which, in other embodiments of the present invention, is also usedby UAS 174 to initiate test events. UAS 174 also defines and implementsadditional interfaces, for example: IAppointment interface 176; IPrintinterface 198; and ITransfer interface 199. IAppointment interface 176transfers examinee candidate information and appointment details fromUAS 174 to test driver 110, as is illustrated by the dashed arrowconnecting IAppointment interface 176 to test driver 110. IPrintinterface 198 allows UAS 174 to send print requests to printer 198regarding reports, for example, score reports. ITransfer interface 199allows UAS 174 to request the transfer of information from candidateexam results file 180 back to UAS 174.

Test driver 110 defines various interfaces to allow test driver 110 tocommunicate with different parts of computer-based test delivery system100. Test driver 110 includes, for example, ten COM interfaces 169 tocommunicate and transfer data with plugins 150. (See Table 1 above) TheCOM interfaces 169 are denoted in FIG. 8 as follows, for example:IDisplay interface 169 a; IHelm interface 169 b; IItem interface 169 c;IUnitTimer interface 169 d; ISelection interface 169 e; INavigateinterface 169 f; IScore interface 169 g; IResults interface 169 h;IReport interface 169 i; and IPlugin interface 169 j.

Test driver 110 and plugins 150 communicate and transfer data with examresource file 120 using, for example, three IPersistResource interfaces192: IPersistResourceStream interface 192 a; IPersistResourceSetinterface 192 b; and IPersistResourceStore interface 192.IPersistResource interfaces 192 are used by plugins 150 duringcompilation of exam source files 130 and are used by both test driver110 and plugins 150 during delivery of the test. During compilation ofexam source files 130, XXL compiler 140 directs plugins 150 in whichstorage location of exam resource file 120 to store any information thatplugins 150 have validated. Plugins 150 can then retrieve the storedinformation from exam resource file 150 during delivery of the test.Other number of interfaces and different combinations of functionalitymay alternatively be used.

Information is saved from plugins 150, or from XXL compiler, 140 ingeneral, to exam resource file 120, for example, as either a stream ofdata, as a set of data, or as a storage structure, depending on which ofthe three IPersistResource interfaces 192 is implemented to save theinformation from plugins 150, to exam resource file 120.IPersistResourceStream interface 192 a saves the information, forexample, as a stream of data. A stream of data is simply a stream ofbytes stored as a linear sequence. IPersistResourceSet interface 192 bsaves the information, for example, as a set of data. A set of data ispreferably a name-value property pair. For example, the name of aparticular property for an item is distractors and the value is thenumber of distractors required for that item. IPersistResourceSetinterface 192 allows the name-value property pair to be saved togetherin exam resource file 120. IPersistResourceStore interface 192 c savesthe information, for example, in a directory format with storage areas.The directory format allows other streams of data to be saved within thestorage area and for sub-storages to be saved under the storage area.

IPersistInstance interface 196, likewise, comprises, for example, three,different interfaces, for example: IPersistInstanceStream interface 196a; IPersistInstanceSet interface 196 b; and IPersistInstanceStoreinterface 196 c. Examination state information is saved to exam instancefile 170, for example, as either a stream of data, as a set of data, oras a storage element, depending on which of the three IPersistResourceinterfaces 192 is implemented.

Two of the interfaces, IContainerNotify interface 200 andIContainerNotifyHelm interface 206, function as callback interfaces fromplugins 150 to test driver 110. IContainerNotify interface 200 allows avisible plugin to inform test driver 110, for example, that the pluginis displayed and ready for examinee interaction. IContainerNotifyHelminterface 206 allows helm plugin 154 to request navigation from testdriver 110 after receiving an input from the examinee to move to anothersection of the test. IMore interface 202 is used to convey whether theexaminee has seen all content in a presentation. For example, a “more”button appears in place of the next button when the content exceeds thewindow length. when the examinee scrolls to the bottom, the “more”button disappers and is replaced with the “next” button. Collectioninterface 204 is used by test driver 110 to hold any group entities, forexample, categories and sections of the test.

The remaining interfaces are, for example, Microsoft defined ActiveDocument interfaces, used to implement OLE linking functions of testdriver 110 and the visible plugins, display plugin 152, helm plugin 154,and item plugin 156. IOleInPlaceFrame interface 210 controls thecontainer's top-level frame window, which involves allowing thecontainer to insert its menu group into the composite menu, install thecomposite menu into the appropriate window frame, and remove thecontainer's menu elements from the composite menu. IOleInPlaceFrameinterface 210 sets and displays status text relevant to the end-placeobject. IOleInPlaceFrame interface 210 also enables or disables theframes modeless dialogue boxes, and translates accelerator key strokesintended for the container's frame. IOleInPlaceUI window interface 211is implemented by container applications and used by object applicationsto negotiate boarder space on the document or frame window. Thecontainer provides a RECT structure in which the object can placetoolbars and other similar controls, determine if tools can in fact beinstalled around the objects' window frame, allocates space for theboarder, and establishes a communication channel between the object andeach frame and document window. IAdviseSync interface 212 enablescontainers and other objects to receive notifications of data changes,view changes, and compound-document changes occurring in objects ofinterest. Container applications, for example, require suchnotifications to keep cached presentations of their linked and embeddedobjects up-to-date.

Calls to IAdviseSync interface 212 methods are a synchronous, so thecall is sent and then the next instruction is executed without waitingfor the calls return. IOleWindow interface 213 provides methods thatallow an application to obtain the handle to the various windows thatparticipate in-place activation, and also to enter and exitcontext-sensitive help mode. IOleInPlaceSite interface 214 managesinteraction between the container and the objects in-place client site.The client site is the display site for embedded objects, and providesposition and conceptual information about the object. IOleClientSiteinterface 215 is the primary means by which an embedded object obtainsinformation about the location and extent of its display site, itsmoniker, its user interface, and other resources provided by itscontainer. Test driver 110 called IOleClientSite interface 215 torequest services from the container. A container must provide oneinstance of IOleClientSite interface 215 for every compound-document itcontains. IOleDocumentSite interface 216 enables a document that hasbeen implemented as a document object to bypass the normal activationsequence for in-place-active objects and to directly instruct its clientsite to activate it as a document object. A client site with thisability is called a “document site”.

B. Core Classes

FIGS. 9A and 9B illustrate the main classes of test driver 110 and theinterfaces between test driver 110 and plugins 150. Also shown are theclasses that interface to UAS 174. ITransfer interface 199, IPrintinterface 198, ILaunch2 interface 177, and IAppointment interface 176represent the connections from test driver 110 to UAS 174, as describedpreviously. Some of the lines depicted in FIG. 9 are solid and some aredashed. The solid lines, for example, between IcResults interface 240and cEvent class 252, represent inheritance. The dashed lines, forexample, between IExam interface 222 and IPlugin interface 169 j,represent instantiation.

Inheritance, or generalization, relates to a generalized relationshipbetween classes that shows that the subclass shares the structure orbehavior defined in one or more superclasses. A generalized relationshipis a solid line with an arrowhead pointing to the superclass.Instantiation, or dependency, represents a relationship between twoclasses, or between a class and an interface, to show that the clientclass depends on the supplier class/interface to provide certainservices. The arrowhead points to the supplier class/interface. Someservices from a supplier class to a client class include, for example:the client class access a value (constant or variable) defined in thesupplier class/interface; methods of the line class invoke methods ofthe supplier class/interface; and methods of the client class havesignatures whose return class or arguments are instances of the supplierclass/interface. For instantiation, the cardinality of the relationshipis illustrated in FIG. 9 if the relationship represents containment.Cardinality specifies how many instances of one class may be associatedwith a single instance of another class. Cardinality can be shown forrelationships to indicate the number of links allowed between oneinstance of a class and the instances of another class.

Test driver 110 also has several interfaces and implementing classes.Test driver 110 interfaces include, for example: IExam interface 222;IMsgBox interface 224; ICategory interface 232; IForm interface 238;IcResults interface 240; IcReport interface 242; IScript interface 246;ISection interface 250; IPresentation interface 248; and/or IcIteminterface 256. The classes that implement the main interfaces include,for example: cScreenMinimum class 226; cFormGroup class 228; cPluginclass 230; cArea class 234; cTemplate class 236; cActivePlugin class250; and cEvent class 252. The interfaces that are prefaced by “Ic” havenames that already exist for plugins 150 to enact, for example, itemplugin 156 implements IItem interface 169 c. IcItem interface 256,however, is the interface implemented by test driver 110 class citem(not shown). Of course, any number of interfaces may be used, dependingon the necessary functionality.

The core class cExam (not shown) implements ILaunch2 interface 177 sothat UAS 174 can control test driver 110. The appointment object, whichimplements IAppointment interface 176, is the main object UAS 174supplies to test driver 110. The appointment object is available toplugins 150 by way of IPlugin interface 169 j. Furthermore, all plugins150 get access to the test (Iexam) using the IPlugin interface 169,also.

The cExam class selects and delivers the form, using cFormGroup class228 and IForm interface 238. The form delivers results using IcResultsinterface 240, reports using IcReport interface 242, and sectionscontained with in the test using ISection interface 250. Classes thatare in the test delivery chain preferably derive from cEvent class 252.

The cResults class (not shown) delivers a results plugin 166 thatimplements IResult interface 169 i. The cReport class (not shown)delivers a report plugin 168 that implements IReport interface 169 h.The cSection, cGroup, and cForm classes (not shown) use severalinvisible plugins 150 to control the delivery of the test. These plugins150 are timer plugins 158, which implement IUnitTimer interface 169 d,selection plugins 160, which implement ISelection interface 169 e,scoring plugins 164, which implement IScore interface 169 g, andnavigation plugins 162, which implement INavigate interface 169 f. ThecPresentation class (not shown) supplies data to its template for thedisplay of the presentation. The three visible plugins 150 are createdand controlled through cTemplate class 236 and child objects cArea class234. Item plugins 156 have an extension class in the citem class (notshown) that wraps the item plugin 156 and provides generic extendedservices that all item plugins 156 implements. The citem class in testdriver 110 is a wrapper class. The citem class provides two baseservices, for example: generic item functionality and access to itemplugin 156, which is the wrapping function. Item generic functionalityincludes, for example: having an item name, having an item title,determining if the item is scored or un-scored, determining whether theitem has been presented to the examinee, etc. These services are genericto all items and are provided by test driver 110. Item plugins 156perform the actual scoring of the item, which is unique to each itemtype. Item plugins 156 present the content of the item and allow theexaminee to interact with the item. These services are unique to eachitem type.

In addition to the interfaces described previously, test driver 110implements IRegistry interface 220, which allows VB code to access theWindows registry. Test driver 110 also implements ILegacyItem interface258 and ILegacyScore interface 260, which are defined by test driver 110and are implements by certain item plugins 156 and scoring plugins 164.ILegacyItem interface 258 and ILegacyScore interface 260 allow old itemtypes that existed in previous test drivers to report results like theprevious test drivers. For some tests, test driver 110 must reportresults for old item types, which had very specific ways of reportingresults. ILegacyItem interface 258 and ILegacyScore interface 260 allowthe new item plugins 156 that represent old item types to report thislegacy format of information to result plugins 166 trying to imitateprevious test drivers.

A complete description of test driver 110 classes and interfaces isincluded in Appendix (Tab 19 & 20).

IV. POLESS

All persistent storages, exam resource file 120 and exam instance file170, preferably utilize POLESS. POLESS allows data to be embedded,linked, or references as external files from the persistent storage totest driver 110 and Active Document container application 112 (FIG. 3).POLESS supports a hierarchical tree structure with node or branch leveladditions, replacements, and deletions. POLESS also supports optionaldata encryption at the node level. The type of encryption employeddepends on the destination of the information in the persistent storage.For example, different encryption keys may optionally be used for databeing routed to test centers, data being routed to administrative datacenters, and data being routed for client use (e.g., client review).Microsoft Crypto-API is preferably used to perform encryption of data inthe persistent storage. Finally, POLESS also supports optionalcompression at the node level, preferably using Lempal-Zev compression.

POLESS is an extension of OLE structured storage compound documentimplementation. A compound document is a single document that contains acombination of data structures such as text, graphics, spreadsheets,sound and video clips. The document may embed the additional data typesor reference external files by pointers of some kind. There are severalbenefits to structured storage. Structured storage provides file anddata persistence by treating a single file as a structured collection ofobjects known as storage elements and streams. Another benefit isincremental access. If test driver 110 or plugins 150 need access to anobject within a compound file, only that particular object need beloaded and saved, rather than the entire file. Additionally, structurestorage supports transaction processing. Test driver 110 or plugins 150can read or write to compound files in transacted mode, where changesmade can subsequently be committed or reverted.

A. POLESS Components

FIG. 10 shows the major components that support POLESS and theinterfaces that connect the components. POLESS 300 may be either examresource file 120 or exam instance file 170. POLESS 300 utilizes PKwarelibrary component 330 for storage compression and decompression. POLESS300 uses Crypto API component 332, a Microsoft application, for storageencryption and decryption. Crypto API component 332 relies on a cryptoservice provided (“CSP”) 334 to perform the actual encryptionalgorithms. Access to the services of these components is facilitated bystandard API interfaces exposed by these components.

OLE2SS component 310 contains all the interface definition that makeupstructure storage. These interfaces can be realized by any structuredstorage implementation, such as compound document implementation OLE2320 and POLESS 300. The interfaces include, for example: IStreaminterface 340; ISequentialStream interface 342; IStorage interface 344;and IRootstorage interface 346. POLESS 300 additionally implementsIStreamVB interface 348 and IStorageVB interface 350.

IStreamVB interface 348 supports several functions, for example: ReadVB(); WriteVB( ); Clear( ); Reset( ); get_sName( ); get_oStream( ); andCopyTo( ). ReadVB( ) reads a specified number of bytes to a data array.WriteVB( ) writes the byte data to the stream. Clear( ) clears thestream of all data. Reset( ) sets position to the beginning of thestream. get_sName( ) is a read-only function that returns the name ofthe stream. get_oStream( ) is a read-only function that returns theIStream interface 348. CopyTo( ) copies a source stream to a destinationstream.

IStorageVB interface 350 supports several functions, for example: Clear(); CommittVB( ); RevertVB( ); sElementName( ); bStorage( ); oElement( );CreateStream( ); OpenStream( ); CreateStorage( ); OpenStorage( );get_sName( ); get_oStorage( ); get_nCount( ); GetCompression( );GetEncryption( ); GetCRC( ); CreateStreamLinked( ); CreatePropertyStg(); OpenPropertyStg( ); SetClass( ); RegisterAlias( ); Destroy( ); andget_ElementType( ). Clear( ) clears the storage of all elements.CommittVB( ) causes transacted mode changes to be reflected in theparent. RevertVB( ) discards changes made since the last commit.sElementName( ) returns the name of the element. bStorage( ) returnsTRUE if the element is a sub-storage. oElement( ) returs IStreamVBinterface 348 or IStorage interface VB 350 for the element.CreateStream( ) creates and opens a stream and returns IStreamVBinterface 348.

OpenStream( ) opens a stream and returns IStreamVB interface 348.CreateStorage( ) creates and opens a nested storage and returnsIStreamVB interface 348. OpenStorage( ) opens an existing storage andreturns IStreamVB interface 348. get_sName( ) is a read-only functionthat returns the name of the storage. get_oStorage( ) is a read-onlyfunction that returns IStorage interface 350. get_nCount( ) is aread-only function that returns a count of the elements. GetCompression() returns the status of file compression. GetEncryption( ) returns thestatus of file encryption. GetCRC( ) returns the status of file CRCchecking. CreateStreamLinked( ) creates and opens a linked stream andreturns IStreamVB interface 348. CreatePropertyStg( ) creates and opensa property storage and returns IpropertyStorageVB interface 414.OpenPropertyStg( ) opens a property storage and returnsIpropertyStorageVB interface 414. SetClass( ) sets the CLSID for thestorage. RegisterAlias( ) registers a pluggable protocol. Destroy( )destroys the specified elements. get_ElementType( ) is a read-onlyfunction that returns the type of the element.

B. POLESS Classes

FIGS. 11A and 11B illustrate the main class of POLESS 300, theinterfaces used to implement the classes, and the flow of the creationof streams 424 and storages 426. cFileRoot class 400 is the first objectinstantiated and is used to create a new or open an existing a POLESSfile. cStorageRoot class 406 is returned, which is a slightly overloadedversion of cStorage class 410. From cStorageRoot class 406 creates oropens cStream class 408 and cStorage class 410, from which any streamsor storages and sub-storages of those can be created or opened,respectively. For instance, cStorage class 410 creates cPropertyStorageclass 412, which creates storage for property sets. The classesimplement interfaces that perform operations and/or define attributesthat further define the function or properties of the class. A completedescription of POLESS 300 classes and interfaces is included in Appendix(Tab 21).

1) cFileRoot Class

cFileRoot class 400 is the root POLESS class and controls the creationand opening of all POLESS files. cFileRoot class 400 is generallyinstantiated first before any other POLESS objects can be created,although other sequences are possible. cFileRoot class 400 implementsIFileRoot interface 401, which is collocated in FIG. 10 with cFileRootclass 400. IFileRoot interface 401 is used to open one file at a timeand is not released until all other storage object 426, stream object424, and property storage interfaces are released and the file is readyto be closed. cFileRoot class 400 and IRoot interface support thefollowing operations, for example: StorageFileCreate( );StorageFileOpen( ); CryptoGet( ); bStorageFile( );StorageAmalgamatedGet( ); DeltaFileCreate( ); DeltaFileApply( );GetObjectFromPath( ); CreateStreamFromBSTR( ); MemoryStreamFromStream(); GetPicture( ); and SavePicture( ).

StorageFileCreate( ) creates a new storage file, returns the rootstorage to interface, marks the new structured storage file as a POLESSfile by storing the class ID (“CLSID”) of this class in a stream in theroot storage. StorageFileOpen( ) opens an existing storage file andreturns the root storage interface. CryptoGet( ) gets a defaultconfigured crypto class and should be set and used on the open or createof the storage file. bStorageFile( ) returns true if the file providedis an OLLE structured storage file and not a POLESS storage file.StorageAmalgamatedGet( ) gets an empty small cStorageAmalgamated class404. DeltaFileCreate( ) creates a POLESS difference file by comparingthe original POLESS file to the updated POLESS file. DeltaFileApply( )applies a POLESS delta file and applies the original POLESS file to thedelta file to create an updated POLESS file. GetObjectFromPath( ) usesmonikers to retrieve the object named by the path and returns a pointerto the object retrieved. CreateStreamFromFile( ) creates a structuredstorage stream and populates it with the contents of the file.CreateStreamFromBSTR( ) creates a structures storage stream and fills itwith the specified string. MemoryStreamFromStream( ) is used to copy astream to a newly created memory stream object. GetPicture( ) loads apicture from stream object 424. SavePicture( ) saves the picture intothe stream 426.

2) cCrypto Class

cCrypto class 402 controls the configuration of theencryption/decryption of POLESS 300. cCrypto class 402 has the followingattributes, for example: sProviderName; eProviderType; sContainerName;and sPassword. SProviderName represents the name of CSP 334 being usedto perform the encryption/decryption services. eProviderType is the typeof CSP 334. The field of cryptography is large and growing. There aremany different standard data formats and protocols. These are generallyorganized into groups or families, each of which has its own set of dataformats and way of doing things. Even if two families used the samealgorithm, for example, the RC2 block cipher, they would often usedifferent padding schemes, different key links, and different defaultmodes. Crypto API is designed so that a CSP provider type represents aparticular family. sContainerName is the key name and must be providedby cCrypto class 402. sPassword is an optional password on thepublic/private key pair and can only be entered by a human operator. Thepassword can be used for review disks and their resource files.

cCrypto class 402 implements ICrypto interface 401 and they support thefollowing properties and method, for example: ProviderName; Password;FileType; Algorithm; EnumProviders( ); and EnumAlgorithms( ).Get_ProviderName( ) returns the name of the Crypto provider.Put_ProviderName( ) sets the name of the Crypto provider. Get_Password() and Put_Password( ) are only used for sponsor resource files.Get_FileType( ) gets the file type and put_FileType( ) sets the filetype. Get_Algorithm( ) gets the encryption algorithm and put_Algorithm() sets the encryption algorithm. EnumProviders( ) returns an enumeratorfor the list of installed providers. EnumAlgorithms( ) enumerate a listof algorithms for the current provider.

3) cStorageAmalgamated Class

cStorageAmalgamated class 404 is an implementation of IStorage interface344. cStorageAmalgamated class 404 holds references to an orderedcollection of IStorage objects. When a stream is opened,cStorageAmagalmated class 404 searches the collection of storage objectsin order to find the first storage object that has the requested streamand returns this stream. cStorageAmalgamated class 404 handles compoundstorage resolution and delegates all other work to cStorage class 410.cStorageAmalgamated class 404 is, for example, read-only.cStorageAmalgamated class 404 will not allow stream or storages to becreated but is primarily for reading exam resource file 120.cStorageAmalgamated class 404 implements IStorageAmalgamated interface405. cStorageAmalgamated class 404 and IStorageAmalgamated interface 405support the following operations, for example: StorageAdd( );Clearstorage( ); OpenStorageAmalgamated( ); andOpenPropertyStgAmalgamated( ). StorageAdd( ) adds a new storage to thecollection of storages. Clearstorage( ) clears all the storage objectsfrom the collection. OpenStorageAmalgamated( ) opens a sub-storage ofthe current amalgamated storages in an amalgamated fashion.OpenPropertyStgAmalgamated( ) opens a property storage of the currentamalgamated storages in an amalgamated fashion. Amalgamation isdescribed in greater detail, in the co-pending application filed on thesame date, entitled “EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FORCOMPUTER BASED TESTING,” incorporated herein by reference.

4) cStorageRoot Class

cStorageRoot class 406 is the POLESS implementation of IStorageinterface 344 and IRootstorage interface 346. cStorageRoot class 406handles any storage object 426 that is POLESS specific and thendelegates work to the cStorage class 410. IRootstorage interface 346supports the SwitchToFile( ) operation, which copies the current fileassociated with the storage object to a new file, which is then used forthe storage object and any uncommitted changes. cStorageRoot class 406also implements IPersistFile interface 418, which provides methods thatpermit an object to be loaded from or saved to a disk file, rather thana storage object or stream. Because the information needed to open afile varies greatly from one application to another, the implementationof IPersistFile::Load on the object preferably also open its disk file.IPersistFile interface 418 inherits its definition from IPersist, so allimplementations must also include the GetClassID( ) method of IPersistinterface 418.

5) cStream Class

cStream class 408 is the POLESS implementation of IStream interface 340.cStream class 408 handles any storage object 426 that is POLESS specificand then delegates work to compound document implementation OLE2 320.The specific work includes compression/decompression andencryption/decryption of stream object 424.

IStream interface 340 supports the following operations, for example:Seek( ); SetSize( ); CopyTo( ); Committ( ); Revert( ); LockRegion( );UnlockRegion( ); Stat( ); and Clone( ). Seek( ) changes the seek pointerto a new location relative to the beginning of stream object 424, theend of stream object 424, or the current seek pointer. SetSize( )changes the size of stream object 424. CopyTo( ) Copies a specifiednumber of bytes from the current seek pointer in stream object 424 tothe current seek pointer in another stream object 424. Commit( ) ensuresthat any changes made to a stream object 424 open in transacted mode arereflected in the parent storage object. Revert( ) discards all changesthat have been made to a transacted stream since the last call toIStream::Commit. LockRegion( ) restricts access to a specified range ofbytes in stream object 424. Supporting this functionality is optionalsince some file systems do not provide this operation. UnlockRegion( )removes the access restriction on a range of bytes previously restrictedwith IStream::LockRegion. Stat( ) retrieves the STATSTG structure forthe stream object 424. Clone( ) creates a new stream object thatreferences the same bytes as the original stream but provides a separateseek pointer to those bytes.

IStreamVB interface 348 is an automation friendly version of IStreaminterface 340. IStreamVB interface 348 supports the followingoperations, for example: Read( ); Write( ); Clear( ); Reset( );get_sName( ); get_oStream; and CopyTo( ). Read( ) reads data from streamobject 424. Write( ) writes data, including the entire byte array, tostream object 424. Clear( ) clears stream object 424 of all data. Reset() resets the position in stream object 424 to the beginning of streamobject 424. Get_sName( ) returns the name of the stream. Get_oStream( )returns the IDispatch interface. CopyTo( ) copies the contents of asource stream to a destination stream.

6) cStorage Class

cStorage class 410 is the POLESS implementation of IStorage interface344 and IcStorage interface 411. cStorage class 410 handles any storageobject 426 that is POLESS specific and then delegates work to compounddocument implementation OLE2 320.

IStorage interface 344 supports the following operations, for example:CreateStream( ); OpenStream( ); CreateStorage( ); OpenStorage( );CopyTo( ); MoveElementTo( ); Commit( ); Revert( ); EnumElements( );DestroyElement( ); RenameElement( ); SetElementTimes( ); SetClass( );SetStateBits( ); and Stat( ). CreateStream( ) creates and opens a streamobject 424 with the specified name contained in a storage object.OpenStream( ) opens an existing stream object 424 within a storageobject using specified access permissions. CreateStorage( ) creates andopens a new stream object 424 within a storage object. OpenStorage( )opens an existing storage object 426 with the specified name accordingto the specified access mode. CopyTo( ) copies the entire contents of anopen storage object 426 into another storage object. The layout of thedestination storage object may differ from the layout of the sourcestorage object. MoveElementTo( ) copies or moves a sub-storage or streamobject 424 from one storage object 426 to another storage object.

Commit( ) reflects changes for a transacted storage object 426 to theparent level. Revert( ) discards all changes that have been made to thestorage object 426 since the last IStorage::Commit operation.EnumElements( ) returns an enumerator object that can be used toenumerate storage objects 426 and stream objects 424 contained within astorage object. DestroyElement( ) removes the specified storage object426 or stream object 424 from a storage object. RenameElement( ) renamesthe specified storage object 426 or stream object 424 in a storageobject. SetElementTimes( ) sets the modification, access, and creationtimes of the indicated storage element, if supported by the underlyingfile system. SetClass( ) assigns the specified CLSID to a storageobject. SetStateBits( ) stores state information in a storage object,for example up to 32 bits. Stat( ) returns the STATSTG structure for anopen storage object.

IStorageVB interface 350 is an automation friendly version of IStorageinterface 344. IStorageVB interface 350 supports the followingoperations, for example: Clear( ); Commit( ); Revert( ); sElementName(); bstorage( ); bElement( ); CreateStream( ); OpenStream( );Createstorage( ); Openstorage( ); get_sName( ); getoStorage( );get_nCount( ); GetCompression( ); GetEncryption( ); GetCRC( );CreateStreamLinked( ); CreatePropertyStg( ); OpenPropertyStg( );SetClass( ); RegisterAlias( ); Destroy( ); and get_ElementType( ). Clear( ) clears the storage of all elements, e.g. sub-storages and streams.Commit( ) ensures that any changes made to a storage object opened intransacted mode are reflected in the parent storage. For non-rootstorage objects in direct mode, this method has no effect. For a rootstorage, it reflects the changes in the actual device, for example, afile on disk. For a root storage object open in direct mode, the commit() method is always called prior to releasing the object. Commit( )flushes all memory buffers to the disk for a root storage in direct modeand will return an error code upon failure. Although releasing theobject also flushes memory buffers to disk, it has no capacity to returnany error codes upon failure. Therefore, calling releasing without firstcalling commit( ) causes indeterminate results. Revert( ) discards allchanges that have been made to the storage object since the last Commit() operation.

sElement( ) returns the name of the element. bstorage( ) returns true ifthe element is a sub-storage. bElement( ) returns either iStreamVBinterface 412 or iStreamVB interface 414 or IStorageVB interface 412 forthe selected element. CreateStream( ) creates and opens a stream objectwith the specified name contained in the storage object. Nothing isreturned if the stream cannot be created. OpenStream( ) opens anexisting stream object within this storage object in the specifiedaccess mode. Nothing is returned if the stream cannot be opened.Createstorage( ) creates and opens a new storage object nested withinthe storage object. Nothing is returned if the storage cannot becreated. Openstorage( ) opens an existing storage object with aspecified name in the specified access mode. Nothing is returned if thestorage cannot be opened. Get_sName( ) returns the name of the storage.Get_oStorage( ) returns the IDispatch interface, which exposes objects,methods and properties to programming tools and other applications thatsupport Automation. COM components implement the IDispatch interface toenable access by Automation clients, such as Visual Basic.

Get_nCount( ) returns the count of elements in the storage.GetCompression( ) determines if streams may be compressed in the fileand if enabled streams may optionally be compressed when created.GetCRC( ) indicates whether a cyclic-redundancy-check (“CRC”), or adigital signature, check is to be performed on the file.CreateStreamLinked( ) creates a link to a stream in another POLESS file.CreatePropertyStg( ) creates a property storage. OpenPropertyStg( )opens a property storage. SetClass( ) assigns the specified CLSID to astorage object. RegisterAlias( ) registers an alias to a storage in thePOLESS file for access by the pluggable protocol. Destroy( ) destroysthe specified element. Get_ElementType( ) is a read-only command thatreturns the type of the element.

7) cPropertyStorage Class

cPropertyStorage class 412 implements IPropertyStorage interface 413,which supports the following operations, for example: ReadMultiple( );WriteMultiple( ); DeleteMultiple( ); ReadPropertyNames( );WritePropertyNames( ); DeletePropertyNames( ); SetClass( ); Commit( );Revert( ); Enum( ); Stat( ); and SetTimes( ). ReadMultiple( ) readsproperty values in a property set. WriteMultiple( ) writes propertyvalues in a property set. DeleteMultiple( ) deletes property values in aproperty set. ReadPropertyNames( ) gets corresponding strung names frogiven property identifiers. WritePropertyNames( ) creates or changesstring names corresponding to given property identifiers.DeletePropertyNames( ) deletes string names for given propertyidentifiers. SetClass( ) assigns a CLSID to a property set. Commit( )flushes or commits changes to a property storage object, as is done withthe command IStorage::Commit, described previously. Revert( ) discardsall changes made since the last commit call when a property storage isopened in transacted mode. Enum( ) creates and gets a pointer to anenumerator for properties within a property set. Stat( ) receivesstatistics about a property set. SetTimes( ) sets modification,creation, and access times for a property set.

IPropertyStorageVB interface 414 is an automation friendly version ofIPropertyStorage interface 413 that manages the persistent properties ofa single property set. IPropertyStrorageVB interface 414 supports thefollowing operations, for example: ReadVB( ); WriteVB( ); Delete( );CommitVB( ); RevertVB( ); SetClass( ); get_ncount( ); CopyTo( );GetName( ); WriteMultiple( ); and ReadMultiple( ). ReadVB( ) reads thevalue of a specified property from the property set. WriteVB( ) writes avalue for a specified property to the property set. If the property doesnot exist the property/value pair will be created. If the propertyalready exists, the value will be updated if opened in eAccess_Writemode. Delete( ) removes a property from the property set. CommitVB( )flushes or commits changes to a property storage object, as is done withthe command IStorage::Commit, described previously. RevertVB( ) discardsall changes made since the last commit call when a property storage isopened in transacted mode. SetClass( ) assigns the specified CLSID to aproperty storage object. Get_nCount( ) returns the count of propertiesin the property set. CopyTo( ) copies the contents of the sourceproperty set to a destination property set. GetName( ) returns the nameof the specified property. WriteMultiple( ) writes property values in aproperty set. ReadMultiple( ) reads property values in a property set.

8) cPropertyStorageAmalgamated Class

cPropertyStorageAmalgamated class 416 implementsIPropertyStorageAmalgamated interface 417, which supports the followingoperations, for example: PropertyStorageAdd( ) and ClearStorage( ).PropertyStorageAdd( ) adds a property set to the collection of propertysets. ClearStorage( ) clears the collection of property sets.

C. POLESS Exam Resource File

FIGS. 14 and 15-26 illustrate the POLESS layout of exam resource file120 according to the present invention. Exam resource file 120 storesthe various pieces of compiled information from exam source files 130,as shown in FIG. 6. Exam resource file 120 contains all of the contentrequired to deliver the test. However, where the test is media-intense,exam resource file 120 will contain the core elements for the test with“links” to the external content. XXL compiler 140 and plugins 150 storethe compiled information to exam instance file 120 using one ofIPersistResourceStream interface 192 a, IPersistResourceSet interface192 b, or IPersistResourceStore interface 192 to store the compiledinformation as a stream of data, a set of data, or a storage element,respectively. In a preferred embodiment, the layout of exam resourcefile 120 is in a hierarchical POLESS format that directly implements theformat of the XXL test definition language. The test developer uses theXXL test definition language to create the logic files 230 and datafiles 212 (FIG. 6) of exam source file 130. By having a storagestructure that follows the format of the XXL test definition language,the incremental access aspect of POLESS is easily implemented. XXLcompiler 140 determines the storage location in exam resource file 120that stores a particular piece of compiled information, even informationstored into exam resource file 120 by one of plugins 150.

FIG. 12 illustrates the main storage branches of exam resource file 120,which corresponds to the top-level elements of the XXL test definitionlanguage, denoted by reference numeral 500. The main storage branches ofexam resource file 120 are, for example: exams branch 550; forms branch600; items branch 650; category branch 700; templates branch 750;sections branch 800; groups branch 850; plugins branch 900; data branch950; formGroups branch 1000; attributes branch 1050; scripts branch1100; and message box (“Msgbox”) branch 1150. Other storage branches mayalternatively be used.

Exam branch 550, as seen in FIG. 13, stores, for example, the primaryattributes, properties, and data that govern the test. Exam branch 550can store information for various tests, as is denoted by the three,vertical ellipses. A specific test is identified by the data stored inname attribute storage 552. Again, the various tests may each beidentified, for example, by a different name, as denoted by the solidborder around name attribute storage 552 or other identification scheme.Attributes storage 554 stores, for example, version information 555, andtitle information 556 of the test as a stream of data. Title information556 is optional, as is denoted by the broken border. Any optional,customized information regarding the test is stored in custom properties558 as a property storage. Information relating to the forms of the testare optionally stored in forms property storage 560. A form is a fixedor substantially fixed order of testing events. Many different forms canbe stored in forms storage 560, giving flexibility to test driver 110 incontrolling progression of the test. FormGroups storage 562 optionallystores information relating to a collection of exam forms as a stream ofdata. Preferably, a single form from the formGroup is chosen to deliverto an examinee. The selection of the form from the group is performed bya selection plugin 160. Exam branch 550 preferably contains at least oneforms storage 560 either independently or within formGroups storage 562.Other information relating to the test may be stored under exam branch550. Other storage formats may optionally be used.

Forms branch 600, as seen in FIGS. 14A and 14B, stores, for example, theprimary attributes, properties, and data that govern the progress of thetest. Forms branch 600 can store information for various forms, as isdenoted by the three, vertical ellipses. As described previously, a formis a fixed or substantially fixed order of testing events. A single formis identified by the data stored in name attribute storage 602. Otheridentification formats may optionally be used. Again, the various formsmay each be identified by a different name, as denoted by the solidborder around name attribute storage 602. Attribute storage 604 stores,for example, begin section information 605, end section information 606,event information 607, and optionally stores version information 608,title information 609, skip allowed information 610, restartableinformation 611, with information 612, height information 613, and bitdepth information 614. All information stored in attribute storage 604is stored as a stream of data or other data storage format. Beginsection information 605 and end section information 606 indicates, forexample, respectively which section of the test begins and ends thetest.

Event information 607 indicates, for example, the order of events of thetest for that form. Each event has a name and is prefixed with an eventtype and a colon. Other formats are optional. The event type includes“section”, “report”, and “results”. Version information 608 and titleinformation 609 indicate the version and title of the form,respectively. Skip allowed information 610 indicates, for example,whether or not by default skipping of sections is allowed. Restartableinformation 611 indicates, for example, whether the form can berestarted. Any optional, customized information regarding the form isstored in custom storage 616 as a property set or other data storageformat. Timer storage 628 stores, for example, information relating tohow the form is to be timed as a storage element. Attributes storage 630stores, for example, the names of Timer Plugin 158 to be used with theform. Plugin data storage 632 and plugin data storage 633 store any datanecessary for timer plugin 158 as a storage element and a stream ofdata, respectively. Plugin data storage 632 and plug in data storage 633are optional. Scoring storage 634 stores, for example, informationrelating to the scoring of the form. Attributes storage 636 stores, forexample, the name of scoring plugin 164 to be used with the form. Plugindata 638 and plugin data 639 optionally store any data needed forscoring Plugin 164 as a storage element and a stream of datarespectively.

Items Branch 650, as seen in FIG. 15, stores, for example, the primaryattributes, properties, and data that govern the items, or testquestions, to be delivered to the examinee during the test. Items branch650 can store information for various items, as is denoted by the three,vertical ellipses. A single item is identified by the data stored inname attributes storage 652. Again, the various items may each beidentified by a different name, as denoted by the solid border aroundname attributes storage 652. Attributes storage 654 stores, for example,weight information 654, scored information 655, and optionally storesskip allowed information 656, title information 657, start information658, finish information 659, and condition information 660. Weightinformation 654 indicates, for example, a value used for judging andscoring the item.

In one embodiment, by default an item is given a weight of one inaccordance with one embodiment, but other values may be utilized. Scoredinformation 655 indicates, for example, whether or not the item isscored as opposed to whether the item is being used as an example. Thedefault of scored information 655 is true. Skip allowed information 656indicates, for example, whether the examinee can skip the item withoutanswering. Start information 658 indicates, for example, scriptexecution at the beginning of the item and finish information 659indicates, for example, script execution at the end of the item.Condition information 660 indicates, for example, whether or not thereis a condition on the item being delivered to the examinee. Theinformation stored in attributes storage 654 is stored as a stream ofdata or other data storage format. Data storage 662 and data stream 664store any information regarding the properties of the item. For example,data storage 662 or data stream 664 can store the correct answer of amultiple choice item. Data storage 662 and data stream 664 stored theinformation as a storage element and a stream of data respectively. Anyoptional, customized information regarding the item is stored in customsstorage 666 as a stream of data or other data storage format. Categorystorage 668 stores, for example, information relating to each categoryto which the item belongs. The information stored in category storage668 preferably and optionally is redundant, as category branch 700stores, for example, all the items within the specific categories. Thereason for the optional redundancy is so that test driver 110 canquickly look up the category of any item.

Category branch 700, as seen in FIG. 16, stores, for example, theprimary attributes, properties, and data that govern the testcategories. A test category provides a grouping mechanism, which isindependent of delivery of the test, allowing for exotic reporting andscoring if necessary. Category branch 700 is optional as denoted by thebroken border. Category branch 700 can store information for variouscategories, as is denoted by the three, vertical ellipses. A singlecategory is identified by the data stored in name attributes storage702. Again, the various categories may each be identified by a differentname, as denoted by the solid border around name attributes storage 702.Attributes storage 704 stores, for example, complete information 705,duplicates information 706, contents information 707, and optionallystores description information 708. Complete information 705 indicates,for example, whether or not every item in the category must appearwithin the category or within its subcategories. Duplicates information706 indicates, for example, whether the item can appear more than oncewithin the category or within the subcategories. Contents information707 determines what can exist within a category. Description information708 is used within the category to contain a description of thecategory's contents. Category storage 710 stores, for example,information relating to any subcategories under the category identifiedin name attribute storage 702. Items storage 712 indicates, for example,any items that exist within the category. Sections storage 714 containsinformation indicating what any sections that exist within the category.Scoring storage 716 contains information relating to the scoring of theitems within the category. Attributes storage 718 stores, for example,the name of the scoring plugin to be used with the item. Data storage720 and data stream 722 contain the information needed to initializescoring plugin 164. Data storage 720 and data stream 722 store theinformation as a storage element and a stream of data respectively.

Templates branch 750, as seen in FIG. 17, stores, for example, theprimary attributes, properties, and data that govern the templates usedin the test. Template branch 750 can store information for various maintemplates, as is denoted by the three, vertical ellipses. A single maintemplate is identified by the data stored in name attributes storage752. Again, the various templates may each be identified by a differentname, as denoted by the solid border around name attributes storage 752.Attributes storage 754 stores, for example, split information 756, orderinformation 757, and optionally stores size information 759. Splitinformation 656 defines how a specific area within the template is to besplit or separated, for example, either by rows or columns. Sizeinformation 759 indicates, for example, possible values for describingthe size of the template, for example, pixels, percentages, or htmlsyntax. Template storage 760 stores, for example, information relatingto any sub-templates to be used under the templates specified by theinformation in name attributes storage 752. Sub-templates are identifiedby the information in name attributes storage 762. Many sub-templates760 can exist as denoted by the three vertical ellipses.

Areas storage 764 indicates, for example, information relating to theareas used within the template denoted by the information in nameattributes storage 752. Many areas may exist within a template asdenoted by the three vertical ellipses. Each area is identified by theinformation stored in name attribute storage 766. Attribute storage 768stores, for example, visible plugin name information 760, sizeinformation 770, and allow more information 771. Plugin name information760 indicates, for example, the name of the visible plugin to be usedwith the area. Size information 770 indicates, for example, the size ofthe area, as for example a pixel value, a percentage value, or HTMLsyntax. Plugin data 772 and plugin data 774 store information relatingto the visible plugin to be used in the area. The data stored in eitherplugin data storage 772 or plugin data stream 774 is executed by thevisible plugin when the template is loaded. Plugin data storage 772 andplugin data stream 774 stores, for example, the information as either astorage element or a stream of data, respectively. Other information mayoptionally be stored.

Section branch 800, as seen in FIG. 18, stores, for example, the primaryattributes, properties, and data that govern test sections. Testsections dictate the navigation and timing of groups of items as well asdisplays within the test. Sections branch 800 can store information forvarious sections, as is denoted by the three, vertical ellipses. Asingle section is identified by the data stored in name attributestorage 802. Again, the various sections may each be identified by adifferent name, as noted by the solid border around name attributesstorage 802. Attributes storage 804 stores, for example, groupinformation 805 and optionally stores title information 806, skipallowed information 807, start information 808, finish information 809,and condition information 810. Group information 805 indicates, forexample, to which group of the test the section belongs. Skip allowedinformation 807 indicates, for example, whether or not the items withinthe section may be skipped. Start information 808 indicates, forexample, script execution at the beginning of the section and finishinformation 809 indicates, for example, script execution at the end ofthe section. Condition information 810 indicates, for example, anyconditions that exist regarding the section. Any optional, customizedinformation regarding this section is stored in custom property storage812 as a stream of data or other data storage format. Custom attributeswill be stored as a property set. The “key” for each attribute will be astring.

Timer storage 814 stores, for example, information regarding the timingof the section. Attribute storage 816 stores, for example, informationidentifying timer plugin 158, which is to be used with a section. Plugindata storage 818 and plugin data storage 820 stores, for example, dataneeded for timer plugin 158. Plugin data storage 818 and plugin datastorage 820 stores, for example, information as a storage element and astring of data or other acceptable format respectively. Navigationstorage 822 stores, for example, information relating to the delivery ofpresentations and groups within the section. Attributes storage 824stores, for example, information indicating which navigation plugin 162is to be used with this section. Plugin data storage 826 and plugin datastream 828 store information needed for the navigation plugin 162.Plugin data storage 826 and plugin data stream 828 store the informationas a storage element and a stream of data respectively. Groups branch850, as seen in FIG. 19, stores, for example, the primary attributes,properties, and data that govern the groups within the test. A groupdetermines the order of events within the test. Groups branch 850 canstore information for various groups, as is denoted by the three,vertical ellipses. A single group is identified by the data store inname attributes storage 852. The various groups may each be identifiedby a different name, as noted by the solid border around name attributesstorage 852. Attributes storage 854 stores, for example, typeinformation 855, event information 856, title information 857, andreviewed name information 858. Type information 855 indicates, forexample, whether the group is either a “group holder” (group ofpresentations), or a “section holder” (group of sub-sections). These aremutually exclusive.

Event information 856 indicates, for example, the order of events withinthe test. Review name information 858 indicates, for example, whether ornot a presentation within the group is to be used as a review screen.Any optional, customized information regarding the group is stored incustom storage 860 as a stream of data or other data storage format.Events storage 862 stores, for example, event information as isdescribed in further detail in FIG. 20. Scoring storage 864 stores, forexample, information relating to the scoring of items within the group.Attributes storage 866 stores, for example, information indicating whichscoring plugin 164 is to be used with the group. Selection storage 872stores, for example, information relating to the selection of itemswithin the group. Attributes storage 874 indicates, for example, whichselection plugin 160 is to be used with the group.

FIGS. 20A, 20B, 20C, and 20D illustrate the events sub-branch of groupsbranch 850 in greater detail in accordance with one embodiment of theinvention. In FIG. 20A, events sub-branch 862 can store information forvarious events. For example, events sub-branch 862 is storinginformation in events name sub-branch 880, event name sub-branch 890,and event name sub-branch 897. Attributes storage 881, in FIG. 20B,under events name storage 880 stores, for example, type information 882,template information 883, and optionally stores title information 884,counted information 885, start information 886, finish information 887,and condition information 888. Type information 882 indicates, forexample, whether the event is an item or a display. Template information883 indicates, for example, which template is being used with the event.Counted information 885 indicates, for example, whether a presentationshould be included in the totals of presentations presented to theexaminee in a section. Generally, presentations with items, orquestions, are counted and introductory presentations are not counted.Start information 886, finish information 887, and condition information888 indicates, for example, start, finish, and conditional scriptsrespectively. Any optional, customized information regarding the eventis stored in custom storage 889. The “key” for each custom attributewill be a string. Event name storage 890 indicates, for example, adifferent event, which contains different attributes. Additionally, areainformation 891 indicates, for example, which area is rendering thepresentations content and item information 892 indicates, for example,the name of the associated item if the event is of the item type.Additionally, data storage 893, data stream 894, data storage 895, anddata storage 896 contain information used in a nested presentation. Thedata off of a nested presentation are the contents of the item or thepresentation. This data may be a stream, a storage, a link to a stream,a link to a storage, or other format. In FIG. 20C, event name 897indicates, for example, another event, which includes a sub-event 898,in FIG. 20D.

Plugins branch 900, as seen in FIG. 21, stores, for example, the primaryattributes, properties, and data that govern any plugins 150 used forthe test. Plugins branch 900 can store information for various plugins,as is denoted by the three, vertical ellipses. A single plugin isidentified by the data stored in name attribute storage 902. A CLSID isstamped with the name of the plugin 150. Attributes storage 904 stores,for example, information identifying the plugin 150 by a program ID.Data storage 906 and data storage 908 store initial data for the pluginas either a storage element or a stream of data respectively.

Data branch 950, as indicated in FIG. 22, stores, for example, anyglobal data needed for the test. Data stored optionally under databranch 950 may be stored as either a storage element or a stream of dataas indicated by data storage 952 and data storage 954. Data stored underdata branch 950 may be directly used by a plugin 150 or the data may beresources (.gif, .jpeg, .wab, .mpeg, etc.) used internally by a plugin150.

FormGroups branch 1000, as seen in FIG. 23, stores, for example, theprimary attributes properties and data that govern the formGroups of thetest. FormGroups branch 1000 can store information for variousformGroups, as is denoted by the three, vertical ellipses. A singleformGroup is identified by the data stored in name attributes storage1002. The various formGroups may each be identified by a different name,as denoted by the solid border around name attributes storage 1002.Attributes storage 1004 stores, for example, information indicatingwhich forms are to be used within the formGroup. Selections storage 1006stores, for example, information relating to the selection of itemswithin the formGroup. Attributes storage 1008 indicates, for example,which selection plugin 160 is to be used with the formGroup. Plugin datastorage 1010 and plugin data storage 1012 store any information neededfor the selection plugin 160. Attributes storage branch 1050 stores, forexample, attribute information that is global to exam resource file 120.This includes the last execution state of XXL compiler 140 [sMode], themajor [iXXLMajorVersion] and the minor version [iXXLMinorVersion] of theXXL language.

Scripts branch 1100 stores, for example, information relating to scriptsused within the test. Attributes storage 1102 stores, for example, typeinformation that specifies which type of language the script is in. Forexample, VB script of J script. Scripts storage 1104 stores, forexample, global scripts used within the test that may be referenced bythe test driver. MsgBox branch 1150 stores, for example, informationrelating to the size and content of any message boxes that may bedelivered to the examinee during the test. Message boxes may betriggered by plugins 150 during the exam.

D. POLESS Exam Instance File

FIGS. 27A, 27B, 27C, and 27D illustrate the POLESS layout of examinstance file 170 according to the present invention. Exam instance file170 stores, for example, information regarding the current examinee'stest. Exam instance file 170 is created when a test starts for anexaminee. Exam instance file 170 is destroyed when the test successfullycompletes. If the examinee must restart her test due to someinterruption, for example, a power failure, the state of the test isrestored from Exam instance file 170. In a preferred embodiment, thelayout of exam instance file 170 is in a hierarchical POLESS format. Asseen in FIG. 27A, the top-level storage branches of exam instance file170 from root 1200 are, for example: running branch 1202; contentsbranch 1310; and history branch 1320. Root 1200 relates to POLESScStorageRoot class 406 (FIG. 27), which instantiates exam instance file170.

Running branch 1202 stores, for example, the state information of allrunning objects in test driver 110 and plugins 150. Plugins 150 use oneof IPersistInstanceStream interface 196 a, IPersistInstanceSet interface196 b, or IPersistInstanceStore interface 196 c to store information toexam instance file 170 as a stream of data, a set of data, or a store ofdata, respectively. Any of plugins 150, except display plugin 152,results plugin 166, report plugin 168, and helm plugin 154, which do notcontain examination state information, store examination stateinformation to exam instance file 170. Test driver 110 determines thestorage location in exam instance file 170 that stores, for example, aparticular piece of examination state information.

Exam sub-branch 1204 contains examination state information relating tothe exam. Contents storage 1206 stores, for example, exam statusinformation 1207 and version information 1208. Exam status information1207 indicates, for example, the status of the exam, for example,initializing or terminating. Template storage branch 1210 stores, forexample, examination state information relating to templates running inthe exam. Name attribute storage 1212 stores, for example, countinformation 1214 and observed ever information 1215. Observed everinformation 1215 indicates, for example, whether or not the template'scontent has ever been fully seen by the examinee.

Form storage branch 1216 contains information relating to the forms usedwithin the exam. Contents storage branch 1218 stores, for example,seconds information 1219, date start information 1220, date finishinformation 1221, current section information 1222, and versioninformation 1223. Current section information 1222 indicates, forexample, the current section being delivered to the examinee in theform. Version information 1223 indicates, for example, theidentification of the form.

Sections chosen storage branch 1224, as illustrated in FIG. 27B, stores,for example, information relating to sections in the form beingdelivered to the examinee. Contents storage 1226 stores, for example,the names of the sections that have been or will be delivered to theexaminee. Name attribute storage 1228 indicates, for example, the nameof a particular section. Contents storage 1230 stores, for example,current child information 1231, seconds information 1232, date startinformation 1233, and date finish information 1234. Navigation storage1236 and navigation storage 1237 store the state information ofnavigation plugin 162. Navigation storage 1236 stores, for example, theexamination state information from navigation plugin 162 if navigationplugin 162 implements the IPersistInterfaceSet 196 b orIPersistInterfaceStore 196 c. Navigation storage 1237 stores, forexample, the information from navigation plugin 162 if navigation plugin162 implements IPersistInterfaceStream 196 a. Timers storage 1238 andtimers storage 1239 store information from timer plugin 158. Timerstorage 1238 is used if timer plugin 158 implements IPersistInterfaceSet196 b or IPersistInterfaceStore 196 c. Timers storage 1239 is used iftimer plugin 158 uses IPersistInterfaceStream 196 a.

Items chosen sub-branch storage 1240 stores, for example, informationrelating to items that have been or will be delivered to the examinee.Contents storage branch 1242 stores, for example, the names and order ofall the items that have been or will be delivered to the examinee. Nameattributes storage 1244 indicates, for example, the identification of aparticular item. Contents storage branch 1246 stores, for example,presented information 1244, complete information 1248, skippedinformation 1249, seconds information 1250, dehydrated information 1251,and observed ever information 1252. Presented information 1247indicates, for example, whether the item has ever been delivered to theexaminee. Completed information 1248 indicates, for example, whether ornot the item has been completed. Skipped information 1249 indicates, forexample, whether the item has been skipped. Item plugin storage 1254 anditem plugin storage 1255 stores, for example, examination stateinformation from item plugin 156. Item plugin storage 1254 is used ifitem plugin 156 uses IPersistInterfaceSet 196 b orIPersistInterfaceStore 196 c. Item plugin storage 1255 is used if itemplugin 156 uses IPersistInterfaceStream 196 a.

In FIG. 27C, item light storage 1256 exists only if the item wasdehydrated (to save memory or when a section ends). The dehydrated itemstores the data but actions on the data are no longer available untilthe item is re-hydrated. Item light storage 1256 stores, for example,score candidate information 1257. Score minimum information 1258, scorenominal information 1259, score maximum information 1260, completeinformation 1261, skipped information 1262, correct answer display 1263,response results 1264, and correct answer results 1266. Timers storage1268 and timers storage 1269 store information from timer plugin 158.Timer storage 1268 is used if timer plugin 158 implementsIPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c. Timersstorage 1269 is used if timer plugin 158 uses IPersistInterfaceStream196 a. Score storage 1270 and Score storage 1271 store information fromtimer plugin 158. Timer storage 1270 is used if timer plugin 158implements IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c.Score storage 1271 is used if timer plugin 158 usesIPersistInterfaceStream 196 a.

Groups chosen sub-branch storage 1272 indicates, for example, whichgroups have been or will be delivered to the examinee. Contents storage1274 stores the names of the groups. Name attributes storage 1276indicates, for example, the name of a particular group. Contents storage1278 stores, for example, names of groups and the order of groups.Scoring storage 1280 and scoring storage 1281 store examination stateinformation from score plugin 164. Scoring storage 1280 is used if scoreplugin 164 implements IPersistInterfaceSet 196 b orIPersistInterfaceStore 196 c. Scoring storage information 1281 is usedif score plugin 164 implements IPersistInterfaceStream 196 a. Selectionstorage 1282 and selection storage 1283 store information from selectionplugin 160. Selection storage 1282 is used if selection plugin 160implements IPersistInterfaceSet 196 b or IPersistInterfaceStore 196 c.Selection storage 1283 is used if selection plugin 160 implementsIPersistInterfaceStream 196 a. Delivered storage 1284, in FIG. 26D,stores, for example, an ordered list of groups chosen for delivery.Delivered storage 1285 stores, for example, an ordered list of thesub-classes of the form, for example: sections, reports and results.

Presentations chosen storage sub-branch 1286 indicates, for example, anypresentations that have been or will be delivered to the examinee.Contents storage 1288 stores, for example, the names of thepresentations. Names storage sub-branch 1290 stores, for example, thename of the presentation. Names storage 1290 also stores, for example,comment information 1291, marked information 1292, count information1293, name information 1294, observed ever information 1295, nameinformation 1296, and observed ever information 1297. Name information1294 and observed information 1295 relate to the name of the firstpresentation area stored under presentations chosen sub-branch 1286 andwhether or not the presentation has ever been observed, and nameinformation 1296 indicates, for example, the last presentation area thatwas delivered to the examinee and whether or not the presentation wasever observed. Contents storage 1298 stores, for example, informationleading to events. Contents storage stores, for example, readyinformation 1299 ever checked information 1300, ever started information1301, and ever finished information 1302. Ready information 1299indicates, for example, whether the event is ready to be delivered tothe examinee. Ever checked information 1300 indicates, for example,whether an event's conditional delivery script ever been checked.Preferably, the conditional delivery script is only checked once. Everstarted information 1301 indicates, for example, whether the event wasever started by the examinee. Ever finished information 1302 indicates,for example, whether the event was completed by the examinee.

Contents branch 1310 stores, for example, a property set containinginformation to identify the examination instance and the examinationstart count 1312. The identifying information used is the examineeappointment identification 1311, the name 1313 of exam resource file120, and the name 1314 of the specified form or group.

History branch 1320 is a single stream of chronological text messagesthat logs the history of the test. These text messages are used by staffat system headquarters to diagnose problems that occurred in the field.Each text message is prefixed with the date, time, and a level ofseverity, for example: information, warning, or error. Test driver 110will filter the text messages to a level of diagnostics desired for testdriver 110, such as determining errors in test driver 110 or detailhistory tracking, including general information.

V. Expansion of Test Driver Using Plugins

FIG. 28 illustrates the process for customizing test based on specificrequirement from the client using plugins 150, denoted generally byreference numeral 1400. First, the client presents the new requirements,for example, a new item type, to the test developer, step 1402. The testdeveloper then writes and XML schema to define the XXL testspecification, step 1404. The schema is subsequently used to validatethe XXL test specification. An example of the XXL schema is as follows:

  <!--   [linear_navigate-schema.xml]    _  -->   <!--===================================================================== -->   <!--   -->   <!-- <linearNavigate>   -->   <!--  -->   <!-- ATTRIBUTE      REQ? DESCRIPTION -->   <!-- initialReview      no  [true] (false) Whether a candidate may  -->   <!--   reviewitems from the very beginning of a  -->   <!--   section.     -->   <!--markAllowed      no  [true] (false) Whether a candidate may  -->  <!--                      mark items during the exam for_review  -->  <!--   purposes.   -->   <!-- incompleteEndAllowed  no      [true](false)_Whether a candidate may    -->   <!--                      enda  section that contains incomplete     -->   <!--   items.     -->  <!-- endSectionPrompt    no      The message to disply when endinga    -->   <!--   section.     -->   <!-- endIncompleteSectionPrompt                        -->   <!--                  no    The message todisplay when ending a  -->   <!--   section with incompleteitems.            -->   <!-- quitExamPrompt    no  The message to displywhen quiting an  -->   <!--   exam.     -->   <!--comment    no  [false] (true)  If the candidate can  -->   <!-- makecomments during this section.  -->   <!-- readOnly    no  [false] (true)If the items are set to  -->   <!-- be read-only.   -->   <!--nextOrMore    no  [true] (false) Whether to show “Next”  -->   <!--  button with “More” button   -->   <!--   -->   <!-- SUB-ELEMENTS   -->  <!-- none   -->   <!--   -->   <!-- NOTES   -->   <!-- -  Non-adaptivenavigation plug-in. -->   <!-- -  Allows for simple “movement” betweenitems and sections    -->   <!-- -  For “markAllowed” to have an effecta_helm which supports marking  -->   <!  -- of items must be used in theexam too. -->   <!-- -  The button labels will appear exactly_as enteredincluding   -->   <!  -- capitalization. -->   <!-- -  It is a commoncase to set comment=“true” and readOnly=“true” and -->  <!--  re-deliver a section for the sole purpose of commenting.    -->  <!--   -->   <!--=====================================================================  -->   <ElementType name=“linearNavigate” order=“many”content=“empty” model=“closed”>     <AttributeType name=“initialReview”dt:type=“enumeration” dt:values=“true false” default=“true”required=“no”/>     <AttributeType name=“markAllowed”dt:type=“enumeration” dt:values=“true false” default=“true”required=“no”/>     <AttributeType name=“incompleteEndAllowed”dt:type=“enumeration” dt:values=“true false” default=“true”required=“no”/>     <AttributeType name=“endSectionPrompt”dt:type=“string” required=“no” default=“This will end your section. Doyou wish to end?”/>     <AttributeType name=“endIncompleteSectionPrompt”dt:type=“string” required=“no” default=“You have not fully answered allitems. If you end incomplete items will be marked as incorrect. Do youwish to end?”/>     <AttributeType name=“quitExamPrompt”dt:type=“string” required=“no” default=“You are about to exit the exam.Do you wish to exit?”/>     <AttributeType name=“comment”dt:type=“enumeration” dt:values=“true false” default=“false”required=“no”/>     <AttributeType name=“readOnly” dt:type=“enumeration”dt:values=“true false” default=“false” required=“no”/>    <AttributeType name=“nextOrMore” dt:type=“enumeration”dt:values=“true false” default=“true” required=“no”/>     <attributetype=“initialReview”/>     <attribute type=“markAllowed”/>    <attribute type=“incompleteEndAllowed”/>     <attributetype=“endSectionPrompt”/>     <attribute type=“quitExamPrompt”/>    <attribute type=“endIncompleteSectionPrompt”/>     <attributetype=“comment”/>     <attribute type=“readOnly”/>     <attributetype=“nextOrMore”/>   </ElementType>The above sample schema is defining the attributes and elementsassociated with the top-level XXL element “linearNavigate.” A moredetail description of the XXL schema is given in the co-pendingapplication filed on the same date, entitled “EXTENSIBLE EXAM LANGUAGE(XXL) PROTOCOL FOR COMPUTER BASED TESTING,” incorporated herein byreference.

The test developer next writes the appropriate plugin 150, in thisexample, item plugin 156. The test developer also implements the IPlugininterface 167 and IPlugin interface and IItem interfaces 169.Additionally, the test developer implements IPersistResource interface192 (FIG. 3) to enable persistence of compiled test information fromitem plugin 156 to exam resource file 120. The test developer canoptionally implement IPersistInstance interface 196 (FIG. 3), step 1408,to enable persistence of examination state information from item plugin156 to exam instance file 170. After the appropriate interfaces havebeen implemented, item plugin 156 is valid and operating. Finally, afterthe test is delivered to the examinee, the result processor accumulatesresults from the examinee, 1410. The results processor must be able tounderstand the new item type to correctly process the results.Customization process 1400 only required the test developer to write onepiece of software, item plugin 156, to accommodate the client'scustomizations rather than multiple pieces of software.

A. Test Production and Test Delivery

FIG. 29 is a flow chart illustrating the overall method of testproduction and test delivery according to the present invention, denotedgenerally by reference numeral 1500. The test publisher first authorsthe test specification and content, step 1502. The test specificationand content are then stored in exam source files 130, step 1504. Examsource files 130, for example, the content of XXL files 134, are thencompiled and validated, step 1506. The compiled test specification andcontent are stored in exam resource file 120, step 1508. Finally, thecompiled test specification and content are delivered to the examinee,step 1510.

The validation of the test specification and content is illustrated ingreater detail in FIG. 30, by the method denoted generally by referencenumeral 1512. When the test specification and content stored in examsource files 130 specifically references a plugin 150, that plugin 150is instantiated, step 1514. Partial test specification and contentrelating to that plugin 150 are loaded into the plugin 150 from examsource files 130, step 1516. In an alternative embodiment, the partialtest specification and content are loaded into a private memory in datacommunication with the plugin 150. The plugin 150 validates the partialtest specification and content, step 1518. The validated testspecification and content are then unloaded from the plugin 150 into astorage element within exam resource file 120.

FIG. 31 illustrates the method of the test delivery cycle in greaterdetail. When the previously validated test specification and contentstored in exam resource file 120 references a plugin 150, the plugin 150is instantiated, step 1525. The storage element in exam resource file120 containing the validated test specification and content are providedto the plugin 150, step 1527. The validated test specification andcontent are loaded into the plugin 150 from the storage element withinexam resource file 120, step 1529. Finally, the examination stateinformation, which includes, for example, the examinee's responses, isstored into exam instance file 170, step 1533.

FIG. 32 illustrates the method of restarting a test after interruptionin greater detail. In test restart method 1535, test driver 110 isstarted, step 1537. Test driver 110 determines whether the test hasalready started, step 1539. If the test delivery has not alreadystarted, plugins 150 reload validated test specification and contentfrom exam resource file 120, step 1543. If the test has already started,plugins retrieve examination information from exam instance file 120,step 1541. Plugins 150 then reload the validated test specification andcontent from exam resource file 120, step 1543. Test driver 110 thendelivers the exam to the examinee, step 1545.

B. Plugin Life Cycle

FIG. 33 illustrates the life cycle of plugin 150 from test production totest delivery, denoted generally by reference numeral 1420. Dashedvertical line 1422 divides the plugin life cycle 1420 into a testproduction cycle, to the left of dashed vertical line 1422, and a testdelivery cycle, to the right of dashed vertical line 1422. The testproduction cycle occurs only occasionally when new plugins 150 aredeveloped to satisfy the requirements of a client. The test deliverycycle occurs whenever the test is delivered to the examinee, forexample, daily.

Exam source files 130, of which data files 132 and XXL files 134 areshown, contain every aspect of the test as written by the testpublisher. In step I, XXL compiler 140 reads from XXL files 134 andinterprets instructions that call for the use of a plugin 150. Plugin150 is identified in the XXL test definition language by both a name anda program identification (“prog ID”). When XXL compiler receives theprog ID from XXL files 134, XXL compiler knows that a plugin 150 isrequired to complete the compilation of exam source files 130. Below isan example of an XXL schema used to define ten plugins 150 of varioustypes:

<?xml version=“1.0” ?> <xxl version=“1.16”xmlns=“x-schema:c:\UTDSDK\xxl-master- schema.xml”>   <!--=====================================================================  -->   <!--     -->   <!--  This contains all of theplugins used for this exam.        -->   <!--     -->   <!--=====================================================================  -->   <!-- TIMERS -->   <plugin name=“clockTime”progid=“UTDP.StandardTimer”/>   <!-- SCORING -->   <pluginname=“testScore” progid=“UTDP.ScoreTable”/>   <!-- RESULTS -->   <pluginname=“testResults” progid=“slsOutputPlugin.cOutputResults”/>   <!--NAVIGATIONS -->   <plugin name=“refNav” progid=“REF.cNavigation”/>  <plugin name=“linearNav” progid=“UTDP.cLinearNavigate”/>   <!--SELECTIONS -->   <plugin name=“sequential”progid=“UTDP.SequentialExhaustive”/>   <!-- DISPLAYS -->   <pluginname=“label” progid=“REF.udLabel”/>   <!-- ITEMS -->   <pluginname=“hotArea” progid=“hotArea.hotAreaItem”/>   <plugin name=“multi”progid=“UTDP.MultiChoiceItem”/>   <!-- HELMS -->   <pluginname=“backForward” progid=“REF.udBackForward”/> </xxl>

The ten plugins defined in the previous example represent eightdifferent types of plugins 150. Not all of the possible types of plugins150 are required to build any one test. Also, more than one plugin 150is implemented for a specific type. In the above example, two navigationplugins 162 and two item plugins 156 are defined. XXL compiler 140 readsinformation from exam source files 130 using IStream interface 340,iNode interface 1424, which is the Microsoft interface used to access anode of an XML document in the document object model (“DOM”), andIStreamVB interface 348. XXL compiler 140 instantiates the requestedplugin 150 using, for example, the call CoCreateInstance.CoCreateInstance( ) creates a single, uninitialized object of the classassociated with a specified CLSID, using a prog ID that has beenconverted into the CLSID.

If the data referring to plugin 150 has been customized by the testdeveloper, XXL compiler 140 may not recognize the new data. Therefore,XXL compiler 140 passes the data directly to plugin 150 and plugin 150loads the data into a private memory (not shown). In one embodiment, theprivate memory is internal to plugin 150, and in another embodiment, theprivate memory is external to plugin 150. Plugin 150 can then validatethe data using the XXL schema. If the data is invalid, plugin 150reports the error. In an alternative embodiment, plugin 150 can validatethe data using an XML document type definition (“DTD”). A DTD is aformal description in XML Declaration Syntax of a particular type ofdocument. Similar to a schema, a DTD sets out what names are to be usedto the different types of elements, where they may occur, and how theyall fit together. However, the XXL schema is preferred for validationsince schemas are easier to read than a DTD and are very flexible.

If plugin 150 declares that the data is valid, XXL compiler 140 preparesa POLESS storage object 300 in exam resource file 120 to which plugin150 saves the data at a command from XXL compiler 140, in step II. Asdescribed previously, XXL compiler 140 determines where the data fromplugin 150 is to be saved in exam resource file 120 and creates theappropriate storage location. The name, CLSID, and data associated withplugin 150 is stored in plugins branch 900 in exam resource file 120(FIG. 21). Plugin 150 implements IPersistResource interface 192 to storethe data to exam resource file 120. Data storage 906 stores, forexample, the data, for example, as either a stream, set of data, or as astorage element if plugin 150 implements either IPersistResourceStream192 a, IPersistResourceSet interface 192 b, or IPersistResourceStoreinterface 192 c, respectively. Data storage 908 stores, for example, thedata as a stream of data if plugin 150 implements IPersistResourceStreaminterface 192 a. Plugin 150 can choose the format used to store the datainto exam resource file 120. Steps I and II are repeated until examsource files 130 are completely compiled and exam resource file 120 iscompletely populated with the compiled test information.

The compile sequence of a plugin 150, as shown in steps I and II in FIG.33, are illustrated in greater detail in FIG. 34. Plugin compilesequence 1430 begins as XXL compiler 140 asks plugin 150 to validate theinformation from exam source files 130 that pertain to plugin 150 usingIPlugin::ValidateSource( ) call 1432, in step I. Plugin 150 validateswhether or not the data received from exam source files 140 is correctlyformatted based on the XXL schema. If the data is not valid, pluginthrows a structured COM error. Plugin 150 does not validate that allrequired source elements are present, but rather, that what is presentis correctly formatted.

Step II contains two steps, indicated as step IIa and IIb. In step IIa,XXL compiler 140 creates the appropriate storage element in examresource file 120 using POLESS object 300. The storage element type isdetermined based on the type of IPersistResource interface 192 thatplugin 150 implements, for example: IPersistResourceStream interface 192a; IPersistResourceSet interface 192 b; or IPersistResourceStoreinterface 192 c. XXL compiler 140 then calls IPersistResource*::Save( )call 1434 for the appropriate IPersistResource interface. Plugin 150saves the compiled information from exam source files 130 to examresource file 120 through the POLESS object 300 passed by XXL compiler140. In step IIb, XXL compiler 140 instructs plugin 150 to unload, orflush, its content using Unload( ) call 1436. As stated previously,steps I, IIa, and IIb are repeated until all of exam source files 130 iscompiled.

Step VI, which is shown as steps VIa and VIb, concerns amalgamation ofexam resource file 120. Amalgamation enables data for a specific pluginto exist virtually as one storage location even if the data appears atdifferent locations within the storage hierarchy. Amalgamation can beperformed on exam resource file 120 if plugin 120 has implemented eitherIPersistResourceSet interface 192 b or IPersistResourceStore interface192 c which storing data to exam resource file 120. In step VIa, XXLcompiler 140 amalgamates one to three storage elements in exam resourcefile 120 and passes the amalgamated POLESS object to plugin 150 usingIPersistResource*::ValidateResource( ) call 1438. Plugin 150 determineswhether or not the amalgamated POLESS object creates a complete andvalid set. Plugin 150 throws a structured COM error if the amalgamatedPOLESS object does not create a complete and valid set. In step VIb, XXLcompiler 140 instructs plugin 150 to unload, or flush, its content usingUnload( ) call 1440. Steps VIa and VIb are interspersed among steps I,IIa, and IIb cycles and can also occur multiple times during thecompilation of exam source files 130. Amalgamation is described ingreater detail, in the co-pending application filed on the same date,entitled “EXTENSIBLE EXAM LANGUAGE (XXL) PROTOCOL FOR COMPUTER BASEDTESTING,” incorporated herein by reference.

Referring again to FIG. 33, during the test delivery cycle, test driver110 reads the test specifications stored in exam resource file 120through POLESS objects 300. Test driver 110 reads information from examresource file 120 through POLESS objects 300 in order to retrieve theencrypted, compressed, and structured elements within exam resource file120. When the XXL test definition language calls a plugin 150 by a progID, as described previously, test driver 110 instantiates the plugin 150that was called, in step III. Test driver 110 provides the POLESS object300 from exam resource file 120 and plugin 150 initializes itself fromthe POLESS object 300, for example, data storage 906 or data storage 908stored under name attribute storage 902, using the appropriateIPersistResource interface 192. The information loaded into plugin 150is the same information as was stored into exam resource file 120 byplugin 150 during the test production cycle (step II). Since plugin 150chose the storage format used to store the information into examresource file 150, plugin 150 can always read the information from examresource file 150, giving plugin 150 complete flexibility. Test driver110 need not be able to read the information that is used by plugin 150.Therefore, any customizations to the test facilitated by plugin 150 doesnot require any changes to test driver 110. The test then progresseswith plugin 150 enhancing the functionality of test driver 110 based onthe new requirements from the client.

Periodically, based on a request either from test driver 110 or fromplugin 150, the state of all running objects will save to exam instancefile 170, which is a unique file for each examinee, indicating theprogress and the status of the test for that examinee. Test driver 110asks plugin 150 if plugin 150 is “dirty,” meaning that plugin 150 isstoring has some updated examination state information. For example,when the examinee selects distractor A on a multi-choice item, itemplugin 156, in this case, becomes dirty. If plugin 150 is dirty, testdriver 110 provides plugin 150 a POLESS object 300 in exam instance file170 and plugin saves the examination state information to exam instancefile 170 using IPersistInstance interface 196, in step IV. For example,item plugin 156 saves the examinee's answer to item plugin storage 1254or to item plugin storage 1255 (FIG. 27). Item storage 1254 stores, forexample, the data as either a set of data or as a storage element ifitem plugin 156 implements either IPersistInstanceSet interface 196 b orIPersistInstanceStore interface 196 c, respectively. Item storage 1255stores, for example, the data as a stream of data if item plugin 156implements IPersistInstanceStream interface 196 a.

Step V occurs if the test is interrupted, for example, because of apower failure, and the test needs to restart. When test driver 110 isrequired to return to a particular operation state, test driver 110reads the examination state information from exam instance file 170.Plugin 150 is provided the storage object containing the state of plugin150 as saved in step IV using IPersistInstance interface 196. Using theprevious example, item plugin 156 retrieves its state information fromitem plugin storage 1254 or for item plugin storage 1255. Plugin 150 isable to become operational from the retrieved state information,enabling a restart of the test from the point at which the test wasinterrupted.

The delivery sequence of a plugin 150, as shown in steps II, IV, and Vin FIG. 33, are illustrated in greater detail in FIGS. 35A, 35B, 35C,and 35D. As seen in FIG. 35A, delivery sequence 1520 particularlyrelates to visible plugins 150, e.g., display plugin 152, helm plugin154, and item plugin 156. Step III contains sub-steps labeled IIIa-IIIb.Plugin delivery sequence 1520 begins, in step IIIa, when the currentdelivering presentation requests its template to activate withIContainerNotifyHelm::Activate( ) call 1524. Activate( ) call 1524 isactivated when the examinee navigates on the test using a helmnavigation control activated by helm plugin 154. IContainerNotifyHelminterface 206 allows helm plugin 154 to request navigation from testdriver 110. IContainerNotifyHelm interface 206 sends Activate( ) call1524 to cTemplate class 236 in test driver 110 (see FIG. 9).

In step IIIb, cTemplate class 236 in test driver 110 uses IPlugin::Load() call 1526 to set the core object references from test driver 110 intothe plugin 150 being delivered. The core object references includeIContainerNotify interface 200, the cExam class (not shown), and theIAppointment interface 176, which passes information regarding theexaminee and appointment to plugin 150.

Step V, which is interspersed with step III, occurs only if the test isinterrupted and plugin 150 loses state. cTemplate class 236 in testdriver 110 uses IPersistInstance*::Reload( ) call 1528 to call on thereload method of exam instance file 170. Exam instance file 170 reloadsplugin 150, through IPersistInstance interface 192, for example,IPersistInstanceSet 192 b, with the state saved to the appropriatestorage location in exam resource file 170 (see FIG. 27).

Step IIIc is performed for both initial delivery of plugin 150 andduring restart of the test, in conjunction with step V. cTemplate class236 in test driver 110 uses IPersistResource*::Load( ) call 1530 to callon the load method of exam resource file 120. Exam resource file 120loads plugin 150, through IPersistResource interface 192, for exampleIPersistResourceSet interface 192 b, with the test specification andcontent from the appropriate storage location in exam resource file 120.Plugin 150 is loaded with test specification and content from examresource file 120 when being initially delivered to the examinee. Plugin150 is also loaded with test specification and content from examresource file 120 and with examination state information from examinstance file 170, as described above, when the test has beeninterrupted and plugin 150 must recover state.

After plugin 150 is properly loaded, cTemplate class 236 in test driver110 uses, I*::PresentationStarting( ) call 1532 (continued in FIG. 35B)to inform visible plugin 150 that the presentation is starting, in stepIIId. I*::PresentationStarting( ) call 1532 is made to any visibleplugin 150 being used in the presentation on the appropriate interface,for example: IDisplay interface 169 a, IItem interface 169 c, or IHelminterface 169 b. For example, an IItem::PresentationStarting( ) call isused for item plugin 156. cTemplate class 236 then instruct visibleplugins 150 to display using IOleObject::DoVerb(Show, . . . ) command1534, step IIIe. IOleObject interface 1522 is the Active Documentinterface used to implement the Active Document presentation. (See FIG.5). IOleObject interface 1522 is the combination of the Active Documentinterfaces described in conjunction with FIG. 8. After instructingvisible plugins 150 to display, test driver 110 awaits notification fromeach visible plugin 150 that the specific visible plugin 150 hassuccessfully shown. Visible plugins 150 call back to test driver 110using IContainerNotify::Activated( ) call 1536, step IIIf. Now, thepresentation is started and active such that the examinee can interactwith the presentation.

The deactivation of the presentation begins with a request from the helmfor navigation. For example, if the examinee has finished a question andwishes to move on to the next question on the next presentation, theexaminee can choose the “NEXT” button on the helm. The navigationrequest is sent from IHelm interface 169 b, which receives the requestfrom the examinee, to test driver 110 using IContainerNotifyHelminterface 206. As seen in FIG. 35D, the request is made usingIContainerNotifyHelm::RequestMove( ) call 1538, step IIIg. Test driver110 then asks each item plugin 156 being used in the presentationtemplate if the examinee is allowed to leave the current presentationand to proceed to the next presentation. The query is made usingIItem::bProceed( ) call 1540, step IIIh. If all item plugins 156 respondin the affirmative, test driver 150 passes the navigation request tonavigation plugin 162, which is an invisible plugin 150. Test driver 110passes the request using INavigate::RequestMove( ) call 1542, step IIIi.Navigation plugin 162 determines the resultant location of the requestednavigation. In FIG. 35, for example, navigation plugin 162 determinesthe section of the test to which the examinee will proceed usingISection::ChildNext( ) call 1544, step IIIj.

The active presentation then instructs the template to deactivate usingcTemplate::Deactivate( ) call 1546, step IIIk (continued in FIG. 35C).Referring back to FIG. 35D, cTemplate class 236 in test driver 110requests that visible plugins 150 hide from the Active Document usingIOleObject::DoVerb(Hide, . . . ) call 1548, step IIIl. cTemplate class236 in test driver 110 informs visible plugins 150 that the currentpresentation is ending using I*::PresentationEnding( ) call 1550, stepIIIm. For example, cTemplate informs helm plugin 154 that the currentpresentation is ending using the IHelm::PresentationEnding( ) call.

Step IV, which contains sub-steps IVa-c, is the process to save pluginstate data to exam instance file 170. Test driver 110 requests the“dirty” state of plugin 150 to determine whether plugin 150 is storingany state information that would be necessary if the test were to beinterrupted. Test driver 110 uses IPersistInstance*::IsDirty( ) call1552 to make the request, step IVa. For example, test driver 110 usesIPersistInstanceSet::IsDirty call 1550 if the state data is a propertyset. If plugin 150 is storing state data that is not already stored inexam instance file 170, IPersistInstance*::IsDirty( ) call 1552 returnstrue. If plugin 150 is “dirty”, test driver 110 instructs plugin 150 tosave the state data to exam instance file 170 in the POLESS objectprovided (FIG. 27) using IPersistInstance*::Save( ) call 1554, step IVb.Finally, test driver 110 instructs plugins 150 to unload all objectsusing IPlugin::Unload( ) call 1556, step IVc.

B. Customizing Test Appearance Using Visible Plugins

1) Templates and Presentations in XXL

The presentation is what is currently seen by the examinee on thedisplay device at a particular instant during the test. When apresentation is rendered, the template is chosen and the screen dividedinto areas. Each area is an Active Document container 112 (FIG. 3) thathosts the specified visible plugin 150 that is an Active Documentserver. The specified visible plugin 150 is chosen by prog ID. FIG. 36shows several different types of areas. Area 1600 is a verticallyelongated rectangle. Area 1602 is a horizontally elongated rectangle.Area 1604 is a square. Areas can take any rectilinear shape as isdictated by the needs of the presentation or template. Other shapesbesides rectangular shapes may optionally be used.

Using XXL, the test publisher can define many templates. Each templateis named and divided into areas. The layout of the template is based onthe division of the screen into areas. Each sub-element of the templatedivides the screen space by rows or columns. This layout technique issimilar to HTML frame sets. The test publisher can use a particulartemplate many times in different presentations, allowing the testpublisher to customize the look of the test. Below is an example of XXLused to define a template:

<template name=“multiItem_Template” split=“rows”>   <areaname=“titlebar” size=“40” plugin=“displayTitlebar”>     <data>      <titlebarHelm done=“false” calc=“false” help=“false” />    </data>   </area>   <area name=“item” plugin=“itemMultiChoice”size=“*” />   <area name=“helm” size=“40” plugin=“helmNextPrevious”>    <data>       <nextPrevious bgcolor=“#D4D0C8”>         <buttonaction=“next” img=“. ./images/continue.bmp” />       </nextPrevious>    </data>   </area> </template>

The template above is named “multiItem_Template”, which divides thedisplay device, e.g., a computer screen, horizontally by rows. The“split” attribute, which in this example has the value “rows”, defineshow the display device is split in the template. “MultiItem_Template”has three areas: “titlebar”; “item”; and “helm”. FIG. 37 shows thelayout of these three areas. The size of “titlebar” area 1610 and “helm”area 1614 are defined at 40 pixels high. The size of “item” area 1612 isdefined by an “*”, which instructs “item” area 1612 to take up anyremaining space not used by “titlebar” area 1610 and “helm” area 1614.

A template is created by combining areas together. Template 1608 isformed by grouping “titlebar” area 1610, “item” area 1612, and “helm”area 1614. It should be noted that there is no rule governing where aparticular area must appear in the template. The test publisher cancreate any type of template using the XXL test definition language. Apresentation is created by containing a visible plugin 150 in each areaof a template. In the XXL example above, as shown in FIG. 37, “titlebar”area 1610 contains “displayTitlebar” display plugin 152, “item” area1612 contains “itemMultiChoice” item plugin 156, and “helm” area 1614contains “helmNextPrevious” helm plugin 154. The areas and plugins 150combine to create presentation 1616. Presentation 1616 displays anon-interactive display in “titlebar” area 1610, a multi-choice item in“item” area 1612, and test navigation controls in “helm” area 1614.

FIG. 38 and FIG. 39 show further examples of templates andpresentations. In FIG. 38, template 1620 is formed by grouping displayarea 1622, display area 1624, item area 1628, and helm area 1626. Thereis no limit on the arrangement of areas with a template and there is norestriction on the type of areas used. In FIG. 39, presentation 1630 isformed by grouping area 1632, which contains an item plugin 156, area1634, which contains an item plugin 156, area 1636, which contains anditem plugin 156, and area 1638, which contains a helm plugin 154. Thereis no display area or display plugin 152 used in presentation 1630.There is no requirement that any particular visible plugin 150 appearwithin a presentation or that all three types of visible plugins 150must appear within a single presentation.

Typically, each time a template is used, the areas in the templatereceive new data, thus creating a new presentation. The “presentation”XXL element links a template to the data used in the template and placesthe template and related data into the test delivery hierarchy. Someareas in the template may have data defined at the template level. Otherareas will not receive their data until the presentation is defined.Some areas in the template may have data defined at the template levelthat is overridden using amalgamation at the presentation level.

For example, a template “main_temp” defines the data for all areasexcept an area “main_item”. The area “main_item” will have a differentitem, or question, for each different presentation, even though theitems all relate to the same scenario. Below is the XXL for the threepresentations that use the “main_temp” template:

<group name=“group01” >   <selection plugin=“sequential” />   <scoringplugin=“testScore” />   <presentation item=“item101”template=“main_temp” area=“main_item” />   <presentation item=“item102”template=“main_temp” area=“main_item” />   <presentation item=“item103”template=“main_temp” area=“main_item” /> </group>The “group” element contains three “presentation” elements. Each“presentation” element delivers different item data in the “main_item”area.

Templates can be nested to create vertical and horizontal divisions ofthe display device. Below is a more complex description of a template inXXL:

<template name=“main_temp” split=“cols”>   <area name=“title”plugin=“browserDisplay” size=“170” >     <data>       <browserDisplayURI=“displays/titlebar.htm” />     </data>   </area>   <templatename=“rest” split=“rows” size=“*”>     <template name=“top” split=“cols”size=“*”>       <area name=“scenario” plugin=“browserDisplay”size=“60%”    >         <data>           <browserDisplayURI=“displays/train.htm” />         </data>       </area>       <areaname=“main_item” plugin=“multi” size=“40%” />     </template >    <template name=“bottom” split=“cols” size=“170”>       <areaname=“next_helm” plugin=“nextPrevious” size=“4*”    >         <data>          <nextPrevious bgcolor=“#FFFFFF”>             <buttonimg=“images/previou.bmp” action=“previous”    />             <buttonimg=“images/next.bmp” action=“next” />           </nextPrevious>        </data>       </area>       <area name=“calc”plugin=“browserDisplay” size=“3*”  >         <data>          <browserDisplay URI=“displays/calculator.htm” />        </data>       </area>     </template >   </template > </template>

FIG. 40 shows the rendering of “main_temp” template 1640. “Main_temp”template 1640 divides the screen into five areas. “Title” area 1642,“scenario” area 1644, and “calc” area 1650 are display areas containingdisplay plugins 152. The XXL definition for “scenario” area 1644contains further plugin data, “URI” attribute with the value“displays/train.htm”. The “URI” attribute links the XXL definition to anexternal file that contains the multimedia content of “scenario” area1644. The “URI” attribute for display plugin 152 in the XXL definitionfor “title” area 1642 defines the appointment information in the titlebar. “Main_item” area 1646 contains “multi” item plugin 156. “Helm” area1648 contains “nextPrevious” helm plugin 154. The additional data in theXXL definition for “helm” area 1648 defines the appearance of the testnavigation control button. “Calc” area 1650 contains “browserDisplay”display plugin 152. The “URI” attribute contains a link to aninteractive calculator that the examinee can use during the question.

“Main_temp” template 1640 uses nested sub-templates to create theconfiguration of the five areas. The first sub-template is named “rest”.The “rest” template defines the appearance of the screen after “title”area 1642 has been rendered. “Title” area 1642 splits the screen intocolumns and has a “size” defined as 170 pixels wide. The “rest” templatesplits the remainder of the screen into rows. The “size” attribute forthe “rest” template is defined with an “*” so that its size is limitedonly by the size of “title” area 1642.

The “rest” template has two sub-templates named “top” and “bottom”. The“top” template contains “scenario” area 1644 and “main_item” area 1646.The “top” template splits its portion of the screen into columns. The“size” attribute for the “top” is defined with the indeterminate and is,therefore, limited in size only by the “bottom” template. “Scenario”area 1644 has a “size” attribute that defines “scenario” area 1644 astaking up 60% of the space available in the “top” template while the“size” attribute of “main_item” area 1646 limits “main_item” area 1646to 40% of the available space.

The “bottom” template contains “next_helm” area 1648 and “calc” area1650. The “bottom” template also splits its portion of the screen intocolumns. The “bottom” template is defined by its “size” attribute asbeing 170 pixels high. The “size” attribute for “next_helm” area 1648 isdefined as “4*” while the “size” attribute for “calc” area 1650 isdefined as “3*”, meaning that “next_helm” area takes up 4/7

$\left( \frac{4}{\left( {4 + 3} \right)} \right)$the amount of space as does “calc” area 1650 within the space availablewithin the “bottom” template.

2) HTML Aspects of Templates and Presentations

Active Document plugins 150 make use of a visible control to renderHTML. Test driver 110 utilizes a browser control that encapsulates thecore portion of Internet Explorer. The browser control uses HTMLrendering capabilities, script interpretation (VBscript and Jscript),Java applet support and Active-X control support.

Multi-choice item plugin 156 is utilized in “main_item” area 1646.Multi-choice item plugin 156 houses the browser control and uses thebrowser control to render the HTML containing the question stem andpossible responses, or distracters. In an alternative embodiment,extensible HTML (“XHTML”) is used. XHTML, which has many of the sameelements as HTML, has a slightly different syntax than HTML to conformto the rules of XML. Below is the HTML used in “main_item” area 1646:

<body background=“RS:trainback.gif” bgproperties=“fixed”>  <!------  ITEM (item1) ------- -->   <div id=“item1” border=“1”>    <blockquote>       <p>         <!-------- STEM TEXT --------- -->        What is the relative velocity of the two trains?       </p>      <form>         <blockquote>           <p>             <inputtype=“radio” value=“A”             id=“Aitem1” name=“item1” />            <label for=“Aitem1” accesskey=“A”>     <!-- Distractor ATEXT --------- -->     A. 20 MPH</label></p>           <p>            <input type=“radio” value=“B”             id=“Bitem1”name=“item1” />             <label for=“Bitem1” accesskey=“B”>     <!--Distractor B TEXT --------- -->     B. 60 MPH     </label></p>          <p>             <input type=“radio” value=“C”            id=“Citem1” name=“item1” />             <label for=“Citem1”accesskey=“C”>     <!-- Distractor C TEXT --------- -->     C. 80 MPH    </label></p>           <p>             <input type=“radio” value=“D”            id=“Ditem1” name=“item1” />             <label for=“Ditem1”accesskey=“D”>     <!-- Distractor D TEXT --------- -->     D. 140 MPH    </label></p>       </form>     </blockquote></blockquote>   </div></body>

The code above is standard HTML. Multi-choice item plugin 156 links upto the input elements by way of the browser control in order to controlthe appearance of the item.

In some cases, the test publisher needs to access test driver 110objects to display core or plugin 150 properties. For example, “title”area 1642 contains information about the examinee, the test, the form,the section, and the time. All of this information exists in the testdriver 110 objects. The browser supports script interpretation usingWindows Scripting Host (“WSH”). The scripting environment is grantedaccess to test driver 110 object by was of the “Window.External” object.Below is a portion of the HTML for “title” area 1642:

<p>   Appointment:<br>   <table border=“2” style=“border-style:inset”>    <tr>       <td>         <SCRIPT Language=“VBSCRIPT”>          Document.write Window.External.oAppointment.sAppointmentID        </SCRIPT>       </td>     </tr>   </table>   Candidate:<br>  <table border=“2” style=“border-style:inset”>     <tr>       <td>        <SCRIPT Language=“VBSCRIPT”>           Document.writeWindow.External.oAppointment.sName         </SCRIPT>       </td>    </tr>   </table>   City:<br>   <table border=“2”style=“border-style:inset”>     <tr>       <td>         <SCRIPTLanguage=“VBSCRIPT”>           Document.writeWindow.External.oAppointment.Properties.Item(“CandidateCity ”).Value        </SCRIPT>       </td>     </tr>   </table> </p> <p>   Exçm:<br>  <table border=“2” style=“border-style:inset”>     <tr>       <td>        <SCRIPT Language=“VBSCRIPT”>           Document.writeWindow.External.oExam.sTitle         </SCRIPT>       </td>     </tr>  </table>   Form:<br>   <table border=“2” style=“border-style:inset”>    <tr>       <td>         <SCRIPT Language=“VBSCRIPT”>          Document.write Window.External.oForm.sTitle         </SCRIPT>      </td>     <tr>   </table>   Section:<br>   <table border=“2”style=“border-style:inset”>     <tr>       <td>         <SCRIPTLanguage=“VBSCRIPT”>           Document.writeWindow.External.oSection.sTitle         </SCRIPT>       </td>     </tr>  </table> </p>

In the above example, the appointment object, exam object, form object,and section object are all referenced from the “Window.External”property.

Further, test driver 110 implements an Internet Explorer pluggableprotocol. The pluggable protocol supplies the requested data from examresource file 120 using composite moniker interfaces. The compositemoniker interfaces allow resolution of hyperlinks to test content data.Exam resource file 120 is an OLE structure storage accessed with thecomposite moniker interfaces.

A standard HTML web page will reference other pages (hyperlinks) andmulti-media via the HTTP protocol. Use of the HTTP protocol requirestransfer of content from a separate file over the internet or anintranet. Such transfer requirements are not acceptable incomputer-based testing. Individual pages could be missing, thecommunications could be unavailable, or the transmissions could beintercepted.

Test driver 110 solves the problem of unreliability by placing allcontent in the encrypted exam resource file 120 using POLESS. To allowthe test publisher the flexibility of HTML and still provide thereliability and security of a single file, test driver 110 utilizes thepluggable protocol. Asynchronous pluggable protocols enable developersto create pluggable protocol handlers, MIME filters, and namespacehandlers that work with Microsoft Internet Explorer and a URL moniker.

POLESS implements the pluggable protocol to allow direct access tostorage elements within exam resource file 120. Test driver 120registers data branch 950 of exam resource file 120 with POLESS underthe protocol prefix “RS”. Therefore, the test publisher can referenceother pages with hyperlinks and multi-media data in the HTML. Byprefixing the name with the “RS:”, the items will be fetched from examresource file 120. Below is the HTML for “scenario” area 1644:

<html>   <body bgproperties=“fixed” scroll=“no”>     <center>      <table border=“2” bgcolor=“white”>         <tr>           <td>            <p>Scenario:</p>             <p><i>Train A</i> left Chicagoheading east to New York at               60 MPH. At the              same time, <i>Train B</i> left New York heading west to              Chicago at 80               MPH. The distance from NewYork to Chicago is 788 miles.</p>           </td>         </tr>      </table>       <p><img border=“2” src=“RS:ChicagoNY.gif”width=“410” height=“198”></p>       <table border=“0” bgcolor=“white”cellpadding=“2”>         <tr>           <td><img border=“2”src=“RS:train.jpg” width=“296” height=“198”></td>           <td>From:CHICAGO, IL US             <p>             To: NEW YORK, NY US<p>            Total Distance: 788 miles</td>         </tr>       </table>    </center>   </body> </html>The “img” element in the above HTML references embedded images using the“src” attribute and the “RS” protocol.

2) Items

Items defined in XXL are made up of two components: a visual componentand a properties component. The visual component controls what theexaminee sees on the display device and is rendered using HTML, asdescribed above. The properties component controls the attributes of anitem, e.g., the correct answer for the item, the weight of the item, theminimum number of responses for the item, etc. The item's visualcomponent and properties component are stored under item branch 650 indata storage 662 or data stream 664 in exam resource file 120 (FIG. 15).

Every item defined in the test specification is given a name. In XXLfiles 134, in exam source files 130, the item is given a property name,i.e., “quest01”. In HTML file 138, also in exam source files 130, theitem is wrapped in a <div> tag which contains the same identificationfor the item. Therefore, the XXL definition for the item is:

<item name=“quest01” . . . </item>The HTML definition for the same item is:

<div id = quest01> . . . </div>

The XXL test definition language along with HTML can be used to definemany different types of items. Some common item types include, forexample: multi-choice items, hot area items, and fill-in-the-blank oressay items. All items are rendered using a combination of XXLdefinition and HTML definition. And example of the XXL and HTMLdefinitions of a multi-choice item follows:

XXL: <item   name=“985”   templates=“multiQuest”area=“main”   weight=“1.0” scored=“true”    skipAllowed=“false” > <data><multiChoice    correctAnswer=“B” autoPrompt=“false” minResponses=“1”maxResponses=“1” URI=“item_bank.htm1#985” /> </data> </item> HTML: <divid=“985”  border=“1”> <blockquote> <p>How do you feel today? </> <form><p><input type=“radio” valuer=“A” id=“A985” name=“985”/> <labelfor=“A985” accesskey=“A”> A. Happy </label> </p> </p><input type=“radio”value=“B” id=“B985” name=“985” /> <label for=“B985” accesskey=“B”> B.Sad  </label> </p> </p><input type=“radio” value=“C” id=“C985”name=“985” /> <label for=“C985” accesskey=“C”> C. A bit Kylish </label></p> </form> </blockquote> </div>

FIG. 41 illustrates the visual rendering of item “985”. The “985”identifier for the item is used in both the XXL definition and the HTMLdefinition. According to the attributes defined in the XXL definition,item “985” appears in area “main” of template “multiQuest”. Item “985”is a scored item that is weighted as one point and may not be skipped bythe examinee. The <data> tag assigns further properties to item “985”.In the above example, the correct answer to item “985” is “B” and onlyone response is allowed for the item. Finally, the “URI” attributeassigns the visual rendering of item “985” to the above HTML file.

FIGS. N-7 to N-12 illustrate further examples of the use of items inpresentations. FIG. 42 shows a multi-choice item presentation usinggraphical distracters in a touch screen environment. Presentation 1651has title area 1652, item area 1653, and helm area 1660. Title area 1652contain display plugins 152 that present a variety of displayinformation, such as, the examinee's name, Hans Bader, the number of thecurrent item, the fact that the test is a demonstration, and the timeremaining in the test. Item area 1653 contains an item plugin 156 thatdefines a multi-media visual 1654 and touch screen graphical distractors1656, 1657, 1658, and 1659 using an “URI” attribute that defines arelated HTML file. Helm area 1660 contains a helm plugin 154 thatprovides a variety of test navigation controls.

FIG. 43 shows review screen 1662, presents the results of thedemonstration test shown in FIG. 42. Title area 1663 contains displayplugins 152 that present information about the examinee, the fact thatthe current presentation is a review screen, and the time elapsed forthe test. Main area 1664 contain display plugin 152 that presentinformation about the examinee's performance on the test. Helm area 1665contains a helm plugin 1665 that provides a variety of test navigationcontrols.

FIG. 44 shows another touch screen multi-choice item. Presentation 1666has title area 1667, scenario area 1668, item area 1669, and helm area1670. Title area 1667 contains display plugins 152 that present variousinformation about the examinee and the test. Scenario area 1668 containsa display plugin 152 with a “URI” attribute that defines an HTML stemand a graphic. Item area 1669 contains an item plugin 156 that presentstouch screen distracters using an “URI” attribute that defines a relatedHTML file. Helm area 1670 contains a helm plugin 154 that provides avariety of test navigation controls.

FIG. 45 shows a multi-choice item that utilizes hyperlinks. Presentation1672 has title area 1673, scenario area 1674, item area 1676, and helmarea 1677. Title area 1673 contains display plugins 152 that presentvarious information about the examinee and the test. Scenario area 1674uses a variety of display plugins 152 to display a prompt, “Select thebest answer,” and a calculator rendered using an “URI” attribute.Scenario area 1674 also presents a stem that uses both text andhyperlinks 1675. Item area 1676 contains an item plugin 156 thatpresents touch screen distracters using an “URI” attribute that definesa related HTML file. Helm area 1677 contains a helm plugin 154 thatprovides a variety of test navigation controls.

FIG. 46 shows a multi-choice item that utilizes scrollbars. Presentation1678 has title area 1679, scenario area 1680, item area 1682, and helmarea 1683. Title area 1679 contains display plugins 152 that presentvarious information about the examinee and the test. Scenario area 1680uses a variety of display plugins 152 to display a prompt, “Select thebest answer,” and a calculator rendered using an “URI” attribute.Scenario area 1674 also presents a stem that uses scrollbar 1681 toenable the examinee to view the entire text of the question. Item area1682 contains an item plugin 156 that presents a large number ofdistracters using scrolling list. Helm area 1683 contains a helm plugin154 that provides a variety of test navigation controls.

FIG. 47 shows a “fill-in-the-blank” type item that requires the examineeto manipulate an active Excel spreadsheet. Presentation 1684 has titlearea 1685, display area 1686, item area 1687, and helm area 1688. Titlearea 1685 contains display plugins 152 that present various informationabout the examinee and the test. Display area 1686 uses a displayplugins 152 to display two prompts and a calculator rendered using an“URI” attribute. Item area 1687 uses a “URI” attribute to define amoniker link to an active Excel spreadsheet stored within exam resourcefile 120. The spreadsheet is fully embedded as an Active Document objectand is fully controlled by test driver 110. Helm area 1688 contains ahelm plugin 154 that provides a variety of test navigation controls.

The many features and advantages of the invention are apparent from thedetailed specification, and thus, it is intended by the appended claimsto cover all such features and advantages of the invention, which fallwithin the true spirit and scope of the invention. Further, sincenumerous modifications and variations will readily occur to thoseskilled in the art, it is not desired to limit the invention to theexact construction illustrated and described, and accordingly, allsuitable modifications and equivalence may be resorted to, fallingwithin the scope of the invention.

1. A system for computer based testing for at least one test, the atleast one test having a customizable presentation format and datacontent, stored in a computer readable media comprising: a test driverthat delivers the at least one test to an examinee using a displaydevice and controls progression of the at least one test; a templatemodule, in operative data communication with the test driver, thatstores in a computer readable medium customizable presentation formatinformation comprising the customizable presentation format of the atleast one test, the customizable presentation format information beingaccessible to the test driver; a data module, in operative datacommunication with the test driver and the template module, that storesin a computer readable medium data content information comprising thedata content of the at least one test, the data content informationbeing accessible to the test driver; and the test driver combining thecustomizable presentation format information with the data contentinformation to create the customizable presentation format and the datacontent of the at least one test, wherein the combining by the testdriver comprises rendering a first customizable presentation format anda first data content and rendering a separately defined secondcustomizable presentation format and second data content, wherein theseparately defined second customizable presentation format and seconddata content provide separate formatting and functionality with respectto the first customizable presentation format and the first datacontent, while being rendered by the test driver for delivery to theexaminee.
 2. The system of claim 1, wherein the data module comprises aplug-in.
 3. The system of claim 1, wherein the customizable presentationformat information segments the display device into a predeterminednumber of areas in a predetermined arrangement.
 4. The system of claim3, wherein the template module further comprises the predeterminednumber of areas in the predetermined arrangement.
 5. The system of claim3, wherein the data content stored in the data module combines with atleast one of the predetermined number of areas to create thepresentation format and data content of the at least one test.
 6. Thesystem of claim 1, wherein the data content information stored in thedata module comprises at least one of non-interactive display material,test navigation controls, and items.
 7. The system of claim 6, whereinthe customizable presentation format information segments the displaydevice into a predetermined number of areas in a predeterminedarrangement, and wherein the data content information combines with thepredetermined number of areas such that the non-interactive displaymaterial, the test navigation controls, and the items comprise separateones of the predetermined number of areas.
 8. The system of claim 1,wherein the data content information and the customizable presentationformat information are combined using active document technology.
 9. Thesystem of claim 1, wherein the data content information furthercomprises a visual component and a properties component, and wherein thevisual component determines a customizable visual aspect of the datacontent, and wherein the properties component determines an attributecomponent of the data content.
 10. The system of claim 9, wherein thecustomizable visual component of the data content information compriseshypertext markup language.
 11. The system of claim 10, wherein thecustomizable visual component references additional visual informationusing a browser pluggable protocol.
 12. The system of claim 10, whereinthe customizable visual component of the data content information iscapable of accessing the properties component of the data contentinformation such that the test driver is capable of presentingup-to-date information regarding the at least one test to the examineeand the progression of the at least one test is capable of beingvisually tracked by the examinee.
 13. The system of claim 9, wherein thecustomizable visual component of the data content information is capableof referencing additional visual information that is not stored withinthe data module.
 14. The system of claim 13, wherein the customizablevisual component of the data content information references theadditional visual information using monikers.
 15. The system of claim13, wherein the additional visual information comprises multimedia data.16. The system of claim 9, wherein the properties component of the datacontent is defined using extensible markup language.
 17. The system ofclaim 1, further comprising a function interface that enablescommunication between the test driver and the data module, wherein thefunction interface enables the test driver to load core objectreferences into the data module at a start of a test delivery cycle andto unload the core object references from the data module at acompletion of the test delivery cycle.
 18. The system of claim 1,further comprising a feature interface that enables the test driver toinstruct the data module to combine the data content information storedin the data module with the customizable presentation format informationstored in the template module.
 19. The system of claim 18, wherein thefeature interface comprises a component object model interface.
 20. Thesystem of claim 18, further comprising a combine function interface thatenables the data content stored in the data module to combine with thecustomizable presentation format information stored in the templatemodule and displayed on the display device.
 21. The system of claim 20,further comprising a notification interface that enables the data moduleto notify the test driver that the data module has successfully combinedthe data content information stored in the data module with thecustomizable presentation format information stored in the templatemodule.
 22. The system of claim 1, further comprising a navigatenotification interface that enables the test driver to receive a requestfrom the examinee to progress through the at least one test.
 23. Thesystem of claim 22, wherein the data content information comprises aplurality of items, the items comprising at least one test question,further comprising a feature interface that enables the test driver todetermine whether the examinee has completed the at least one testquestion such that the examinee is authorized to progress through the atleast one test.
 24. The system of claim 22, further comprising anavigation interface that enables the test driver to control theprogression of the at least one test.
 25. The system of claim 24,further comprising a section interface that enables the test driver toidentify a subsequent section of the at least one test to which the atleast one test should progress after receiving a request from theexaminee to progress through the at least one test.
 26. The system ofclaim 1, further comprising a resource file, in operative datacommunication with the template module and the data module, the resourcefile storing the data content information and progression informationrelating to the progression of the at least one test, the data contentinformation being accessible to the data module.
 27. The system of claim26, wherein the template module is stored within the resource file suchthat the resource file stores the customizable presentation formatinformation of the at least one test.
 28. The system of claim 26,wherein the resource file comprises a structure storage database, andwherein the template module is stored as an object within the resourcefile.
 29. The system of claim 26, wherein the data content informationand the progression information of the at least one test compriseextensible markup language format.
 30. The system of claim 29, whereinthe template module is stored within the resource file, such that theresource file stores the customizable presentation format information,and the template module comprises extensible markup language format. 31.The system of claim 26, wherein the data module retrieves the datacontent information from the resource file.
 32. The system of claim 31,wherein the data content information stored in the resource file furthercomprises a visual aspect component that determines a visual aspect ofthe data content.
 33. The system of claim 31, wherein the customizablevisual component of the data content information is capable ofreferencing additional visual information, and wherein the additionalvisual information is stored in the resource file.
 34. The system ofclaim 33, wherein the customizable visual component of the data contentinformation references the additional visual information stored in theresource file using monikers.
 35. The system of claim 33, wherein theadditional visual information comprises multimedia data.
 36. The systemof claim 26, further comprising a resource persistence interface thatenables communication between the data module and the resource file suchthat the data module is capable of retrieving the data contentinformation from the resource file.
 37. The system of claim 1, furthercomprising an instance file in operative data communication with thetest driver and the data module, the instance file storing examinationstate information comprising responses provided by the examinee to itemspresented to the examinee during the at least one test.
 38. The systemof claim 37, wherein the instance file comprises a structure storagedatabase.
 39. The system of claim 37, further comprising an instancepersistence interface that enables communication between the data moduleand the instance file such that the data module is capable of storingthe examination state information to the instance file and retrieve theexamination from the instance file, wherein, if the at least one test isinterrupted, the data module is capable of retrieving the examinationstate information that was provided by the examinee before the at leastone test was interrupted, combine the retrieved examination stateinformation with the customizable presentation format information storedin the template module, and enable the examinee to continue with the atleast one test in situ.
 40. The system of claim 39, further comprising:a resource file in operative data communication with the template moduleand the data module, the resource file storing the customizablepresentation format information, the data content information, andprogression information relating to the progression of the at least onetest; and a resource persistence interface that enables communicationbetween the data module and the resource file such that the data moduleis capable of retrieving the data content information from the resourcefile, wherein, if the at least one test is interrupted, the data moduleis capable of retrieving the data content information of the at leastone test, combine the data content information retrieved from the datamodule with the customizable presentation format information stored inthe template module, and enable the examinee to continue with the atleast one test in situ.
 41. The system of claim 40, wherein the templatemodule is stored within the resource file.
 42. The system of claim 1,wherein a portion of the customizable presentation format information isoverridden by another portion of the customizable presentation formatinformation using amalgamation.
 43. The system of claim 1, wherein thecustomizable presentation format information and the data contentinformation is arranged in a hierarchy.
 44. A system for computer basedtesting for at least one test, the at least one test having acustomizable presentation format and data content, stored in a computerreadable media comprising: a test driver that delivers the at least onetest to an examinee using a display device and controls progression ofthe at least one test; a template module, in operative datacommunication with the test driver, that stores in a computer readablemedium customizable presentation format information comprising thecustomizable presentation format of the at least one test, thecustomizable presentation format information being accessible to thetest driver; a data module, in operative data communication with thetest driver and the template module, that stores in a computer readablemedium data content information comprising the data content of the atleast one test, the data content information being accessible to thetest driver; the test driver combining the data content information withthe customizable presentation format information to create thecustomizable presentation format and data content of the at least onetest, wherein a portion of the customizable presentation formatinformation is overridden by the data content information usingamalgamation as the customizable presentation format is changed toreceive the data content information during the combining by the testdriver; a resource file, in operative data communication with thetemplate module and the data module, that stores in a computer readablemedium the progression of the at least one test, the resource fileproviding the customizable presentation format information to thetemplate module and providing the data content information to the datamodule and; an instance file in operative data communication with thetest driver and the data module, the instance file storing in a computerreadable medium examination state information comprising responsesprovided by the examinee to items presented to the examinee during theat least one test.
 45. The system of claim 44, wherein the templatemodule further comprises a predetermined number of areas in apredetermined arrangement, wherein: the customizable presentation formatinformation segments the display device into the predetermined number ofareas in the predetermined arrangement; the data content informationcombines with at least one of the predetermined number of areas usingactive document technology to create the customizable presentationformat and data content of the at least one test, the data contentinformation being one of non-interactive display material, testnavigation control, and items; and the data content information combineswith the predetermined number of area such that the non-interactivedisplay material, the test navigation control, and the items compriseseparate ones of the predetermined number of areas.
 46. The system ofclaim 44, wherein customizable presentation format is nested inproviding the at least one test.
 47. A system for computer based testingfor at least one test, the at least one test having a customizablepresentation format and data content, stored in a computer readablemedia comprising: a test driver that delivers the at least one test toan examinee using a display device and controls progression of the atleast one test; a template module, in operative data communication withthe test driver, that stores in a computer readable medium customizablepresentation format information comprising the customizable presentationformat of the at least one test, the customizable presentation formatinformation dividing the display device into a predetermined number ofareas in a predetermined arrangement, the customizable presentationformat information being accessible to the test driver; and a first datamodule, in operative data communication with the test driver and thetemplate module, that stores in a computer readable medium firstinformation comprising non-interactive display material of the at leastone test, the first information being accessible to the test driver; asecond data module, in operative data communication with the test driverand the template module, that stores in a computer readable mediumsecond information comprising test navigation controls of the at leastone test, the second information being accessible to the test driver; athird data module, in operative data communication with the test driverand the template module, that stores in a computer readable medium thirdinformation comprising items of the at least one test, the thirdinformation being accessible to the test driver; and the test drivercombines the first information, the second information, and the thirdinformation with the customizable presentation format information tocreate the customizable presentation format and data content of the atleast one test, wherein the customizable presentation format informationand the data content information is arranged in a hierarchy where thehierarchy defines how the data content information appears whendisplayed after being combined with the customizable presentation formatinformation.
 48. A system for computer based testing for at least onetest, the at least one test having a customizable presentation formatand data content, stored in a computer readable media comprising: testdriver means for delivering the at least one test to an examinee using adisplay device and controlling progression of the at least one test;template means, in operative data communication with the test drivermeans, for storing customizable presentation format informationcomprising the customizable presentation format of the at least onetest, the customizable presentation format information being accessibleto the test driver means; and data storage means, in operative datacommunication with the test driver means and the template means, forstoring data content information regarding the data content of the atleast one test, the data content information being accessible to thetest driver means, the test driver means combining the data contentinformation with the customizable presentation format information tocreate the customizable presentation format and data content of the atleast one test, wherein the combining by the test driver means comprisesrendering a first customizable presentation format and first datacontent and rendering a separately defined second customizablepresentation format and second data content, wherein the separatelydefined second customizable presentation format and second data contentprovide separate formatting and functionality than the firstcustomizable presentation format and the first data content, while beingrendered by the test driver means for delivery to the examinee.
 49. Asystem for computer based testing for at least one test, the test havinga presentation format and data content, stored in a computer readablemedia comprising: a test driver that delivers the at least one test toan examinee using a display device and controls progression of the test;a template module, in operative data communication with the test driver,that stores in a computer readable medium customizable presentationformat information comprising the customizable presentation format ofthe test, the customizable presentation format information accessible tothe test driver, wherein a portion of the customizable presentationformat information is overridden by another portion of the customizablepresentation format information using amalgamation; a data module, inoperative data communication with the test driver, that stores in acomputer readable medium data content information comprising the datacontent of the test, the data content information accessible to the testdriver; and a presentation module, in operative data communication withthe test driver, the template module, and the data content module, thatstores in a computer readable medium customizable presentationinformation determining what is seen by the examinee on the displaydevice during delivery of the at least one test, wherein thecustomizable presentation information is defined by combining thecustomizable presentation format information and the data contentinformation to deliver the at least one test where a portion of thecustomizable presentation format information is overridden by the datacontent information using amalgamation as the customizable presentationformat is changed to receive the data content during the combiningprocess.
 50. A method for computer based testing for at least one test,the at least one test having a customizable presentation format and datacontent, the at least one test being controlled by a test driver, whichdelivers the at least one test to an examinee using a display device andcontrols progression of the at least one test, the method comprisingsteps of: retrieving customizable presentation format informationcomprising the customizable presentation format of the at least one testfrom a template module, the customizable presentation format informationdividing the display device into a predetermined number of areas in apredetermined arrangement; retrieving data content informationcomprising the data content of the at least one test from a data module;combining for delivery to the examinee the customizable presentationformat information and the data content information to create thecustomizable presentation format and data content of the at least onetest, wherein the customizable presentation format information and thedata content information is arranged in a hierarchy where the hierarchydefines how the data content information appears when displayed afterbeing combined with the customizable presentation format information;and delivering on the display device the at least one test.
 51. Themethod of claim 50, wherein the data content information stored in thedata module combines with at least one of the predetermined number ofareas to create the customizable presentation format and data content ofthe at least one test.
 52. The method of claim 50, wherein the datacontent information stored in the data module comprises at least one ofnon-interactive display material, test navigation controls, and items.53. The method of claim 52, wherein the data content informationcombines with the predetermined number of areas such that thenon-interactive display material, the test navigation controls, and theitems comprise separate ones of the predetermined number of areas. 54.The method of claim 50, wherein the data content information and thecustomizable presentation format information are combined using activedocument technology.
 55. The method of claim 50, further comprising thestep of notifying the test driver to create a presentation by combiningthe customizable presentation format information stored in the templatemodule with the data content information stored in the data module,wherein the presentation is what is seen by the examinee on the displaydevice at a particular instance during the at least one test.
 56. Themethod of claim 55, wherein the test driver is notified to create thepresentation when the examinee requests to progress through the at leastone test by activating a navigation control interface.
 57. The method ofclaim 50, further comprising the step of loading core object referencesfrom the test driver into the data module at a start of a test deliverycycle.
 58. The method of claim 50, wherein the data content informationis stored in a resource file, further comprising the step of loading thedata content information from the resource file into the data module.59. The method of claim 50, retrieving the data content information fromthe data module further comprising the step of notifying the data modulethat a new presentation is being created using a feature interface,wherein the presentation is what is seen by the examinee on the displaydevice at a particular instance during the at least one test, andwherein the presentation is created by combining the customizablepresentation formation information and the data content information. 60.The method of claim 59, wherein the data content information comprisesat least one of non-interactive display material, test navigationcontrols, and items and the feature interface enables the test driver tonotify the data module that a particular one of the non-interactivedisplay material, the test navigation controls, and the items is to becombined with the customizable presentation format information.
 61. Themethod of claim 50, further comprising the step of notifying the testdriver that the data content information in the data module hassuccessfully combined with the customizable presentation formatinformation in the template module.
 62. The method of claim 50, furthercomprising the step of loading examination state information from aninstance file into the data module, wherein the examination stateinformation includes responses provided by the examinee to itemspresented to the examinee during the at least one test, and wherein, ifthe at least one test is interrupted, the data module is capable ofretrieving the examination state information that was provided by theexaminee before the at least one test was interrupted, combine thecombine the retrieved examination state information with thecustomizable presentation format information stored in the templatemodule, and enable the examinee to continue with the at least one testin situ.
 63. The method of claim 62, further comprising the steps of:sending an inquiry to the data module to determine whether the datamodule is storing the examination state information; and saving theexamination state information from the data module to the instance file,wherein the data module is capable of subsequently loading theexamination state information from the instance file if the at least onetest is interrupted.
 64. The method of claim 62, wherein the datacontent information is stored in a resource file, further comprising thestep of loading the data content information from the resource file intothe data module, wherein, if the at least one test is interrupted, thedata module is capable of retrieving the data content information,combine the retrieved data content information with the customizablepresentation format information stored in the template module, andenable the examinee to continue with the at least one test in situ. 65.The method of claim 50, further comprising the step of notifying thetest driver to deactivate a current presentation by separating the datacontent information from the customizable presentation formatinformation, wherein the current presentation is what is then currentlyseen by the examinee on the display device at a particular instanceduring the at least one test.
 66. The method of claim 65, wherein the atleast one test driver is notified to deactivate the current presentationwhen the examinee requests when the examinee requests to progressthrough the at least one test by activating a navigation controlinterface.
 67. The method of claim 65, wherein the data contentinformation stored in the data module comprises a plurality of items,the items comprising at least one test question, further comprising thestep of sending a request to the data module to determine whether theexaminee has completed the at least one test question such that theexaminee is authorized to progress through the at least one test. 68.The method of claim 65, further comprising the steps of identifying asubsequent section of the at least one test to which the at least onetest should progress; and navigating to the subsequent section of the atleast one test if the examinee has completed the at least one testquestion.
 69. The method of claim 50, further comprising the step ofunloading core object references from the data module into the testdriver at a completion of a test delivery cycle.